diff options
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | 2009-04-04 04:25:48 +0000 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2009-04-04 03:14:52 -0400 |
| commit | 2586d5663d0a17d69383acf6110f16a979a07c4e (patch) | |
| tree | 5bfe1ef88ee03084175bb94c4c1079402fefbe7b /kernel/lockdep_internals.h | |
| parent | 73a94d86a8625371f76de0ee12dc5bacd3ed42c0 (diff) | |
| download | kernel-crypto-2586d5663d0a17d69383acf6110f16a979a07c4e.tar.gz kernel-crypto-2586d5663d0a17d69383acf6110f16a979a07c4e.tar.xz kernel-crypto-2586d5663d0a17d69383acf6110f16a979a07c4e.zip | |
thinkpad-acpi: remove HKEY disable functionality
The HKEY disable functionality basically cripples the entire event
model of the ThinkPad firmware and of the thinkpad-acpi driver.
Remove this functionality from the driver. HKEY must be enabled at
all times while thinkpad-acpi is loaded, and disabled otherwise.
For sysfs, according to the sysfs ABI and the thinkpad-acpi sysfs
rules of engagement, we will just remove the attributes. This will be
done in two stages: disable their function now, after two kernel
releases, remove the attributes.
For procfs, we call WARN(). If nothing triggers it, I will simply
remove the enable/disable commands entirely in the future along with
the sysfs attributes.
I don't expect much, if any fallout from this. There really isn't any
reason to mess with hotkey_enable or with the enable/disable commands
to /proc/acpi/ibm/hotkey, and this has been true for years...
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'kernel/lockdep_internals.h')
0 files changed, 0 insertions, 0 deletions