From: Stas Sergeev <stsp@list.ru>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org,
Linux kernel <linux-kernel@vger.kernel.org>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Kyungmin Park <kyungmin.park@samsung.com>,
Stas Sergeev <stsp@users.sourceforge.net>
Subject: Re: [PATCH] leds: fix brightness changing when software blinking is active
Date: Thu, 14 May 2015 12:45:16 +0300 [thread overview]
Message-ID: <55546EAC.70408@list.ru> (raw)
In-Reply-To: <55546084.9050704@samsung.com>
14.05.2015 11:44, Jacek Anaszewski пишет:
>
>> if (led_cdev->blink_delay_on || led_cdev->blink_delay_off) {
>> led_cdev->delayed_set_value = brightness;
>> - schedule_work(&led_cdev->set_brightness_work);
>
> This line is still required. Please refer to the patch d23a22a74.
But I really want to get rid of this line and
vacate the work-queue, so that in the future the
per-driver work-queues can be replaced with this.
Why do you think it is still needed?
Are there any valid cases where you need to disable the
soft-blink from hard-irq context? IMHO the soft-blink is
only disabled as a result of user's actions, which is not
in a hard-irq context.
Could you please explain the use-case?
>> /* Stop blinking */
>> + led_stop_software_blink(led_cdev);
> This won't be needed.
Indeed, but with these changes there should be no requirement
for disabling a soft-blink from hard-irq context, which is what
I really wanted to have. What am I missing?
next prev parent reply other threads:[~2015-05-14 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:20 [PATCH] leds: fix brightness changing when software blinking is active Stas Sergeev
2015-05-14 8:44 ` Jacek Anaszewski
2015-05-14 9:45 ` Stas Sergeev [this message]
2015-05-14 10:33 ` Jacek Anaszewski
2015-05-14 11:03 ` Stas Sergeev
2015-05-14 11:52 ` Stas Sergeev
2015-05-14 12:09 ` Jacek Anaszewski
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=55546EAC.70408@list.ru \
--to=stsp@list.ru \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=stsp@users.sourceforge.net \
/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