* [RESEND] leds: Ensure hardware blinking turns off when requested
@ 2023-04-05 16:50 Eddie James
2023-04-20 8:22 ` Lee Jones
0 siblings, 1 reply; 2+ messages in thread
From: Eddie James @ 2023-04-05 16:50 UTC (permalink / raw)
To: linux-leds; +Cc: linux-kernel, lee, pavel, Eddie James
If an LED is blinking through the hardware and the trigger is deactivated,
the driver will set the brightness to 0 to disable blinking. However, if
the LED driver doesn't support non-blocking operations, the request for
setting brightness to 0 will get queued. Then if a user requests a new
non-zero brightness before the request for 0 brightness is executed, the
LED blinking will not get disabled since the brightness will simply be
updated.
Fix this by flushing the workqueue before updating the requested
brightness.
Fixes: 4d71a4a12b13 ("leds: Add support for setting brightness in a synchronous way")
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
drivers/leds/led-class.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
index 9255bc11f99d..78a270300d30 100644
--- a/drivers/leds/led-class.c
+++ b/drivers/leds/led-class.c
@@ -57,6 +57,8 @@ static ssize_t brightness_store(struct device *dev,
if (state == LED_OFF)
led_trigger_remove(led_cdev);
+ /* flush out any request to disable blinking */
+ flush_work(&led_cdev->set_brightness_work);
led_set_brightness(led_cdev, state);
flush_work(&led_cdev->set_brightness_work);
--
2.31.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [RESEND] leds: Ensure hardware blinking turns off when requested
2023-04-05 16:50 [RESEND] leds: Ensure hardware blinking turns off when requested Eddie James
@ 2023-04-20 8:22 ` Lee Jones
0 siblings, 0 replies; 2+ messages in thread
From: Lee Jones @ 2023-04-20 8:22 UTC (permalink / raw)
To: Eddie James; +Cc: linux-leds, linux-kernel, pavel
On Wed, 05 Apr 2023, Eddie James wrote:
> If an LED is blinking through the hardware and the trigger is deactivated,
> the driver will set the brightness to 0 to disable blinking. However, if
> the LED driver doesn't support non-blocking operations, the request for
> setting brightness to 0 will get queued. Then if a user requests a new
> non-zero brightness before the request for 0 brightness is executed, the
> LED blinking will not get disabled since the brightness will simply be
> updated.
> Fix this by flushing the workqueue before updating the requested
> brightness.
You make a convincing argument for this.
> Fixes: 4d71a4a12b13 ("leds: Add support for setting brightness in a synchronous way")
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
> drivers/leds/led-class.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> index 9255bc11f99d..78a270300d30 100644
> --- a/drivers/leds/led-class.c
> +++ b/drivers/leds/led-class.c
> @@ -57,6 +57,8 @@ static ssize_t brightness_store(struct device *dev,
>
> if (state == LED_OFF)
> led_trigger_remove(led_cdev);
> + /* flush out any request to disable blinking */
> + flush_work(&led_cdev->set_brightness_work);
> led_set_brightness(led_cdev, state);
> flush_work(&led_cdev->set_brightness_work);
Just to be clear, you want to flush the work before AND after setting
the brightness?
In the commit message, could you make it clear why simply moving this
flush won't work.
--
Lee Jones [李琼斯]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-04-20 8:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-04-05 16:50 [RESEND] leds: Ensure hardware blinking turns off when requested Eddie James
2023-04-20 8:22 ` Lee Jones
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).