| commit | 0a6707c10e04fa056e30bff05a33009170959f42 | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Mon, 16 Jul 2007 18:23:29 +0000 (16 15:23 -0300) | ||
| committer | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Sat, 1 Sep 2007 02:55:35 +0000 (31 23:55 -0300) | ||
| tree | 9463f712e5b5dfac72d3e7b3a820c36f483fb599 | treesnapshot (tar.gz zip) |
| parent | 28f32dfeb369e088fd6acbb1a5ea8122864b0851 | commitdiff |
ACPI: thinkpad-acpi: add locking to brightness subdriver
The backlight class does all the locking needed for sysfs access, but
offers no API to interface to that locking without an layer violation.
Since we need to mutex-lock procfs access, implement in-driver locking for
brightness. It will go away the day thinkpad-acpi procfs goes away, or the
backlight class gives us a way to use its locks without a layer violation.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
The backlight class does all the locking needed for sysfs access, but
offers no API to interface to that locking without an layer violation.
Since we need to mutex-lock procfs access, implement in-driver locking for
brightness. It will go away the day thinkpad-acpi procfs goes away, or the
backlight class gives us a way to use its locks without a layer violation.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
| drivers/misc/thinkpad_acpi.c | diffblobblamehistory |