From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linux-leds@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, andrew@lunn.ch,
sakari.ailus@linux.intel.com,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: [PATCH 0/5] LED flash: Set brightness in a sync way on demand
Date: Mon, 21 Sep 2015 16:29:25 +0200 [thread overview]
Message-ID: <1442845770-17800-1-git-send-email-j.anaszewski@samsung.com> (raw)
Since it has become apparent that user should decide whether brightness
is to be set in a synchronous or an asynchronousi way, export internal
led_set_brightness_sync API and remove SET_BRIGHTNESS_SYNC and
SET_BRIGHTNESS_ASYNC flags from the LED core. After patch set [1] flash
LED drivers don't longer have to implement brightness_set op and use work
queues internally. Remove the redundant code from them.
Thanks,
Jacek Anaszewski
[1] https://lkml.org/lkml/2015/9/16/299
Jacek Anaszewski (5):
leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting
Documentation: leds: Add description of brightness setting API
leds: max77693: Remove work queue
leds: aat1290: Remove work queue
leds: ktd2692: Remove work queue
Documentation/leds/leds-class.txt | 21 ++++++++++++++
drivers/leds/led-class-flash.c | 4 ---
drivers/leds/led-class.c | 2 --
drivers/leds/led-core.c | 33 ++++++++++++---------
drivers/leds/leds-aat1290.c | 50 +++++++++-----------------------
drivers/leds/leds-ktd2692.c | 41 ++++----------------------
drivers/leds/leds-max77693.c | 57 ++++++-------------------------------
drivers/leds/leds.h | 13 ---------
include/linux/leds.h | 19 +++++++++++--
9 files changed, 84 insertions(+), 156 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-09-21 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 14:29 Jacek Anaszewski [this message]
2015-09-21 14:29 ` [PATCH 1/5] leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting Jacek Anaszewski
2015-09-22 6:42 ` Sakari Ailus
2015-09-22 7:09 ` Jacek Anaszewski
2015-09-22 19:16 ` Andrew Lunn
2015-10-08 15:50 ` Pavel Machek
2015-10-09 6:28 ` Jacek Anaszewski
2015-10-09 7:02 ` Pavel Machek
2015-10-09 8:08 ` Jacek Anaszewski
2015-10-09 11:16 ` Pavel Machek
2015-09-21 14:29 ` [PATCH 2/5] Documentation: leds: Add description of brightness setting API Jacek Anaszewski
2015-09-22 10:26 ` Sakari Ailus
2015-09-22 11:03 ` Jacek Anaszewski
2015-09-22 19:27 ` Andrew Lunn
2015-09-23 9:24 ` Jacek Anaszewski
2015-09-21 14:29 ` [PATCH 3/5] leds: max77693: Remove work queue Jacek Anaszewski
2015-09-22 10:28 ` Sakari Ailus
2015-09-21 14:29 ` [PATCH 4/5] leds: aat1290: " Jacek Anaszewski
2015-09-21 14:29 ` [PATCH 5/5] leds: ktd2692: " Jacek Anaszewski
2015-10-08 15:50 ` Pavel Machek
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=1442845770-17800-1-git-send-email-j.anaszewski@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®