diff options
author | Evan Green <evgreen@chromium.org> | 2021-04-02 00:04:36 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-04-02 17:30:21 +0300 |
commit | b0077b4b085f636e5f8a1fd9cd6e568907471b24 (patch) | |
tree | ddc4d3648db91f794da7b40bf529fd98411a7031 /net/batman-adv/distributed-arp-table.c | |
parent | 38ab861493de18c672b101765751f5e6bb17ec0d (diff) | |
download | linux-b0077b4b085f636e5f8a1fd9cd6e568907471b24.tar.xz |
firmware: google: Enable s0ix logging by default
Many moons ago, support was added to the SMI handlers to log s0ix entry
and exit. Early iterations of firmware on Apollo Lake correctly returned
"unsupported" for this new command they did not recognize, but
unfortunately also contained a quirk where this command would cause them
to power down rather than resume from s0ix.
Fixes for this quirk were pushed out long ago, so all APL devices still
in the field should have updated firmware. As such, we no longer need to
have the s0ix_logging_enable be opt-in, where every new platform has to
add this to their kernel commandline parameters. Change it to be on by
default.
In theory we could remove the parameter altogether: updated versions of
Chrome OS containing a kernel with this change would also be coupled
with firmware that behaves properly with these commands. Eventually we
should probably do that. For now, convert this to an opt-out parameter
so there's an emergency valve for people who are deliberately running
old firmware, or as an escape hatch in case of unforeseen regressions.
Signed-off-by: Evan Green <evgreen@chromium.org>
Link: https://lore.kernel.org/r/20210401140430.1.Ie141e6044d9b0d5aba72cb08857fdb43660c54d3@changeid
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/batman-adv/distributed-arp-table.c')
0 files changed, 0 insertions, 0 deletions