diff options
| author | Herton Ronaldo Krzesinski <herton@mandriva.com.br> | 2010-11-30 16:30:43 -0200 |
|---|---|---|
| committer | Matthew Garrett <mjg@redhat.com> | 2011-01-07 17:03:41 -0500 |
| commit | 698e1641a37f833dd26ee2fde5eed426cd97880b (patch) | |
| tree | c0b6bc8bb6e39e813cf3711c7a4fd95d899c4a9f /drivers/thermal/Kconfig | |
| parent | 58f6425eb92f54943878b0b3f9c1e51f99c2cb72 (diff) | |
| download | kernel_samsung_aries-698e1641a37f833dd26ee2fde5eed426cd97880b.zip kernel_samsung_aries-698e1641a37f833dd26ee2fde5eed426cd97880b.tar.gz kernel_samsung_aries-698e1641a37f833dd26ee2fde5eed426cd97880b.tar.bz2 | |
classmate-laptop: little optimization for cmpc_rfkill_block
We don't need to call bios/acpi (cmpc_set_rfkill_wlan) if the blocked
state is already set to the same value (little optimization). This can
happen for example if we initialize the module with same initial
hardware state (rfkill core always call cmpc_rfkill_block on
initialization here).
Also GWRI method only accepts 0 or 1 for setting rfkill block, as can be
seen on AML code from acpidump->DSDT from a classmate sample I have, so
should be fine setting state only to 0 or 1 directly.
Signed-off-by: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Acked-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Diffstat (limited to 'drivers/thermal/Kconfig')
0 files changed, 0 insertions, 0 deletions