From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH] led: core: Fix brightness setting when setting active_off=0
Date: Sat, 23 Dec 2017 11:33:40 +0100 [thread overview]
Message-ID: <a097e3df-1803-4496-0df6-0c4d7f8a54b0@gmail.com> (raw)
In-Reply-To: <95b148d6-6b21-ef67-ff69-ab471222c51d@gmail.com>
Hi Matthieu,
I was to send this fix for 4.15-rc5, but just realized the
possible mistake in the subject. Would you mind if I did
the following amendment?:
s/active_off/delay_off/
--
Best regards,
Jacek Anaszewski
On 12/13/2017 09:16 PM, Jacek Anaszewski wrote:
> Hi Matthieu,
>
> Thanks for catching this. Applied.
>
> On 12/12/2017 11:10 AM, Matthieu CASTET wrote:
>> With the current code, the following sequence won't work :
>> echo timer > trigger
>>
>> echo 0 > delay_off
>> * at this point we call
>> ** led_delay_off_store
>> ** led_blink_set
>> *** stop timer
>> ** led_blink_setup
>> ** led_set_software_blink
>> *** if !delay_on, led off
>> *** if !delay_off, set led_set_brightness_nosleep <--- LED_BLINK_SW is set but timer is stop
>> *** otherwise start timer/set LED_BLINK_SW flag
>>
>> echo xxx > brightness
>> * led_set_brightness
>> ** if LED_BLINK_SW
>> *** if brightness=0, led off
>> *** else apply brightness if next timer <--- timer is stop, and will never apply new setting
>> ** otherwise set led_set_brightness_nosleep
>>
>> To fix that, when we delete the timer, we should clear LED_BLINK_SW.
>>
>> Cc: linux-leds@vger.kernel.org
>> Signed-off-by: Matthieu CASTET <matthieu.castet@parrot.com>
>> ---
>> drivers/leds/led-core.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c
>> index fd83c7f77a95..f3654fd2eaf3 100644
>> --- a/drivers/leds/led-core.c
>> +++ b/drivers/leds/led-core.c
>> @@ -186,7 +186,7 @@ void led_blink_set(struct led_classdev *led_cdev,
>> unsigned long *delay_on,
>> unsigned long *delay_off)
>> {
>> - del_timer_sync(&led_cdev->blink_timer);
>> + led_stop_software_blink(led_cdev);
>>
>> clear_bit(LED_BLINK_ONESHOT, &led_cdev->work_flags);
>> clear_bit(LED_BLINK_ONESHOT_STOP, &led_cdev->work_flags);
>>
>
next prev parent reply other threads:[~2017-12-23 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:10 [PATCH] led: core: Fix brightness setting when setting active_off=0 Matthieu CASTET
2017-12-13 20:16 ` Jacek Anaszewski
2017-12-23 10:33 ` Jacek Anaszewski [this message]
2017-12-27 9:16 ` Matthieu CASTET
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a097e3df-1803-4496-0df6-0c4d7f8a54b0@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).