diff options
author | 2017-02-09 16:44:11 +0100 | |
---|---|---|
committer | 2017-02-24 23:48:51 -0800 | |
commit | 06da5325d02ed3e9be9fbc7d0d621a04efc96961 (patch) | |
tree | 0084fa50385872a0510170481ead2c29534f5c87 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | leds: class: Add new optional brightness_hw_changed attribute (diff) | |
download | wireguard-linux-06da5325d02ed3e9be9fbc7d0d621a04efc96961.tar.xz wireguard-linux-06da5325d02ed3e9be9fbc7d0d621a04efc96961.zip |
platform/x86: thinkpad_acpi: Stop setting led_classdev brightness directly
There is no need to set the led_classdev's brightness value from
its set_brightness callback, this is taken care of by the led-core and
thinkpad_acpi really should not be mucking with it.
Note that kbdlight_set_level_and_update() is still used by the old
thinpad_acpi specific sysfs interface for the led, so we cannot
remove it.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions