diff options
author | Jason Gerecke <jason.gerecke@wacom.com> | 2024-12-09 21:40:29 +0300 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.com> | 2024-12-10 14:41:52 +0300 |
commit | 88006b8eca63467cf1b28fed839f4954c578eeff (patch) | |
tree | 35700fa843103c63f8a238f009737e1b50c78a16 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 8d355b56f29533e0b0db0d9a2de8bdc05ab27375 (diff) | |
download | linux-88006b8eca63467cf1b28fed839f4954c578eeff.tar.xz |
HID: wacom: Initialize brightness of LED trigger
If an LED has a default_trigger set prior to being registered with
the subsystem, that trigger will be executed with a brightness value
defined by `trigger->brightness`. Our driver was not setting this
value, which was causing problems. It would cause the selected LED
to be turned off, as well as corrupt the hlv/llv values assigned to
other LEDs (since calling `wacom_led_brightness_set` will overite
these values).
This patch sets the value of `trigger->brightness` to an appropriate
value. We use `wacom_leds_brightness_get` to transform the llv/hlv
values into a brightness that is understood by the rest of the LED
subsystem.
Fixes: 822c91e72eac ("leds: trigger: Store brightness set by led_trigger_event()")
Cc: stable@vger.kernel.org # v6.10+
Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Signed-off-by: Jiri Kosina <jkosina@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions