| commit | 2d5e94d7ca315f859a0eee1366838e8ad34dd7b2 | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Sat, 26 Apr 2008 04:02:20 +0000 (26 01:02 -0300) | ||
| committer | Len Brown <len.brown@intel.com> | |
| Tue, 29 Apr 2008 13:47:00 +0000 (29 09:47 -0400) | ||
| tree | 3bbf8aff5cc01084984b07da060add73d3c0cd4c | treesnapshot (tar.gz zip) |
| parent | 8c74adbc692a3cb040cc69d7ca3dfd86d75860a8 | commitdiff |
ACPI: thinkpad-acpi: rate-limit CMOS/EC unsynced error messages
If userspace applications mess with the CMOS NVRAM, or something causes
both the ACPI firmware and thinkpad-acpi to try to change the brightness at
the same time, it is possible to have the CMOS and EC registers for the
current brightness go out of sync.
Should that happen, thinkpad-acpi could be really obnoxious when using a
brightness_mode of 3 (both EC and CMOS). Instead of complaining a massive
number of times, make sure to complain only once until EC and CMOS are back
in sync.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Joerg Platte <lists@naasa.net>
Signed-off-by: Len Brown <len.brown@intel.com>
If userspace applications mess with the CMOS NVRAM, or something causes
both the ACPI firmware and thinkpad-acpi to try to change the brightness at
the same time, it is possible to have the CMOS and EC registers for the
current brightness go out of sync.
Should that happen, thinkpad-acpi could be really obnoxious when using a
brightness_mode of 3 (both EC and CMOS). Instead of complaining a massive
number of times, make sure to complain only once until EC and CMOS are back
in sync.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Joerg Platte <lists@naasa.net>
Signed-off-by: Len Brown <len.brown@intel.com>
| drivers/misc/thinkpad_acpi.c | diffblobblamehistory |