summaryrefslogtreecommitdiffstats
path: root/drivers/misc/tifm_7xx1.c
diff options
context:
space:
mode:
authorHenrique de Moraes Holschuh <hmh@hmh.eng.br>2008-04-26 01:02:18 -0300
committerLen Brown <len.brown@intel.com>2008-04-29 09:47:00 -0400
commit92889022250d736e135ca92fbffd1ab0ea4780d1 (patch)
tree156815ba61d29b9e70a593a795077e3eff119fc1 /drivers/misc/tifm_7xx1.c
parentb59727965d7f286489206c292e2788d4835a8a23 (diff)
downloadop-kernel-dev-92889022250d736e135ca92fbffd1ab0ea4780d1.zip
op-kernel-dev-92889022250d736e135ca92fbffd1ab0ea4780d1.tar.gz
ACPI: thinkpad-acpi: warn once about weird hotkey masks
thinkpad-acpi knows for a while now how to best program the hotkeys by default, and always enable them by default. Unfortunately, this information has not filtered down everywhere it needs to, yet. Notably, old ibm-acpi documentation and most "thinkpad setup guides" will have wrong information on this area. Warn the local admin once whenever any of the following patterns are met: 1. Attempts to set hotkey mask to 0xffff (artifact from docs and config for the old ibm-acpi driver and behaviour). This mask makes no real-world sense; 2. Attempts to set hotkey mask to 0xffffffff, which means the user is trying to just have "everything work" without even reading the documentation, or that we need to get a bug report, because there is a new thinkpad out there with new exciting hot keys :-) 3. Attempts to set hotkey mask to 0xffffff, which is almost never the correct way to set up volume and brightness event reporting (and with the current state-of-the-art, it is known to never be right way to do it). The driver will perform any and all requested operations, though, regardless of any warnings. I hope these warnings can be removed one or two years from now. Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/misc/tifm_7xx1.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud