Heinrich Toews
869a9bb515
leds: rgb: wago-m4: switch to brightness_set_blocking
...
wago_led_set() acquires send_lock (a mutex) and is therefore a
sleeping function. Assigning it to brightness_set violates the LED
core API contract: brightness_set is called directly from atomic
context (timer/softirq) and must not sleep. On non-RT kernels this
would trigger BUG: scheduling while atomic.
Use brightness_set_blocking instead. The LED core automatically
defers calls through a workqueue, making the sleeping path safe.
Update the function signature to return int and add return 0 as
required by the blocking callback prototype.
Reported-by: Oleg Karfich <oleg.karfich@wago.com >
Signed-off-by: Heinrich Toews <ht@twx-software.de >
2026-06-18 18:13:10 +02:00
..
2025-06-04 14:42:15 +02:00
2025-06-20 09:56:35 -05:00
2025-06-04 14:42:01 +02:00
2025-06-19 15:28:36 +02:00
2025-06-19 15:28:00 +02:00
2025-06-19 15:28:23 +02:00
2025-07-02 10:00:41 +02:00
2025-07-02 10:00:41 +02:00
2025-06-04 14:42:06 +02:00
2025-06-19 15:28:31 +02:00
2025-06-19 15:27:59 +02:00
2025-06-04 14:42:05 +02:00
2025-06-19 15:28:03 +02:00
2025-07-02 09:59:58 +02:00
2025-06-19 15:28:04 +02:00
2025-10-10 18:26:10 +02:00
2025-06-19 15:28:14 +02:00
2025-06-19 15:28:31 +02:00
2025-07-02 10:00:41 +02:00
2025-07-02 10:00:41 +02:00
2025-06-19 15:28:26 +02:00
2025-06-19 15:28:31 +02:00
2025-07-02 10:00:41 +02:00
2025-06-04 14:42:21 +02:00
2025-07-02 10:00:41 +02:00
2025-06-19 15:28:18 +02:00
2025-07-02 10:00:41 +02:00
2025-06-19 15:28:16 +02:00
2026-06-18 18:13:10 +02:00
2025-06-04 14:41:54 +02:00
2025-06-19 15:28:26 +02:00
2025-06-04 14:42:12 +02:00
2025-07-02 10:00:41 +02:00
2025-07-02 10:00:41 +02:00
2025-11-17 12:32:57 +01:00
2025-07-02 10:00:41 +02:00
2026-06-18 18:08:43 +02:00
2026-03-17 17:54:09 +01:00
2026-03-17 17:54:08 +01:00
2025-06-04 14:41:56 +02:00
2025-06-19 15:28:43 +02:00
2025-06-19 15:28:29 +02:00
2025-06-19 15:28:08 +02:00
2025-06-19 15:28:29 +02:00
2025-07-02 10:00:41 +02:00
2025-06-04 14:42:25 +02:00
2025-06-04 14:42:07 +02:00
2025-06-19 15:28:05 +02:00
2025-06-19 15:28:38 +02:00
2025-07-02 10:00:41 +02:00
2026-06-18 11:14:16 +02:00
2025-06-19 15:28:27 +02:00
2025-07-02 10:00:41 +02:00
2025-06-04 14:41:53 +02:00
2025-06-19 15:28:40 +02:00
2025-06-19 15:28:25 +02:00
2025-06-04 14:42:17 +02:00
2026-03-17 17:54:09 +01:00
2025-06-19 15:28:06 +02:00
2025-06-04 14:42:10 +02:00
2025-06-04 14:42:20 +02:00
2025-06-19 15:28:30 +02:00
2025-07-02 10:00:41 +02:00
2025-06-19 15:28:37 +02:00
2025-07-02 10:00:41 +02:00
2025-06-04 14:42:05 +02:00
2025-06-19 15:28:17 +02:00
2025-06-04 14:42:05 +02:00
2025-06-19 15:28:26 +02:00
2025-11-05 10:42:11 +01:00
2025-06-19 15:28:09 +02:00