summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/Makefile
diff options
context:
space:
mode:
authorTony Vroon <tony@linx.net>2009-02-02 11:11:10 +0000
committerLen Brown <len.brown@intel.com>2009-02-21 21:59:55 -0500
commit4898c2b2f04051e19f4230683c0f0b15f71af887 (patch)
tree45c1e916e5dccd8f0583f6f836483e6c9811840a /drivers/acpi/Makefile
parentadfafefd104d840ee4461965f22624d77532675b (diff)
downloadop-kernel-dev-4898c2b2f04051e19f4230683c0f0b15f71af887.zip
op-kernel-dev-4898c2b2f04051e19f4230683c0f0b15f71af887.tar.gz
fujitsu-laptop: Use RFKILL support bitmask from firmware
Up until now, we polled the rfkill status for every incoming FUJ02E3 ACPI event. It turns out that the firmware has a bitmask which indicates what rfkill-related state it can report. The rfkill_supported bitmask is now used to avoid polling for rfkill at all in the notification handler if there is no support. Also, it is used in the platform device callbacks. As before we register all callbacks and report "unknown" if the firmware does not give us status updates for that particular bit. This was fed through checkpatch.pl and tested on the S6420, S7020 and P8010 platforms. Signed-off-by: Tony Vroon <tony@linx.net> Tested-by: Stephen Gildea <stepheng+linux@gildea.com> Acked-by: Jonathan Woithe <jwoithe@physics.adelaide.edu.au> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud