summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorJason Gerecke <jason.gerecke@wacom.com>2024-12-09 10:40:29 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-02-01 18:39:39 +0100
commit5f5e6cbc4f5e5888c4b5ef22c9d5adc361fcc66f (patch)
treeefe9ea17939a2733ba38691570b5e2e212b03c7b /tools/perf/scripts/python/stackcollapse.py
parent5e1bde45daba1e8d4f650b2d3ec188252b8120d4 (diff)
downloadkernel-5f5e6cbc4f5e5888c4b5ef22c9d5adc361fcc66f.tar.gz
HID: wacom: Initialize brightness of LED trigger
commit 88006b8eca63467cf1b28fed839f4954c578eeff upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions