From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linux-leds@vger.kernel.org, linux-media@vger.kernel.org
Cc: kyungmin.park@samsung.com, b.zolnierkie@samsung.com,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: [PATCH/RFC v6 0/2] LED / flash API integration - LED Flash Class drivers
Date: Mon, 22 Sep 2014 17:22:18 +0200 [thread overview]
Message-ID: <1411399340-16458-1-git-send-email-j.anaszewski@samsung.com> (raw)
This patch set is the follow-up of the LED / flash API integration
series [1]. For clarity reasons the patchset has been split into
four subsets:
- LED Flash Class
- V4L2 Flash
- LED Flash Class drivers
- Documentation
========================
Changes since version 5:
========================
- removed flash manager framework - its implementation needs
further thorough discussion.
- removed external strobe facilities from the LED Flash Class
and provided external_strobe_set op in v4l2-flash. LED subsystem
should be strobe provider agnostic.
Thanks,
Jacek Anaszewski
[1] https://lkml.org/lkml/2014/7/11/914
Jacek Anaszewski (2):
leds: Add support for max77693 mfd flash cell
leds: Add driver for AAT1290 current regulator
drivers/leds/Kconfig | 15 +
drivers/leds/Makefile | 2 +
drivers/leds/leds-aat1290.c | 460 ++++++++++++++++++
drivers/leds/leds-max77693.c | 1083 ++++++++++++++++++++++++++++++++++++++++++
4 files changed, 1560 insertions(+)
create mode 100644 drivers/leds/leds-aat1290.c
create mode 100644 drivers/leds/leds-max77693.c
--
1.7.9.5
next reply other threads:[~2014-09-22 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 15:22 Jacek Anaszewski [this message]
2014-09-22 15:22 ` [PATCH/RFC v6 1/2] leds: Add support for max77693 mfd flash cell Jacek Anaszewski
2014-09-22 15:22 ` [PATCH/RFC v6 2/2] leds: Add driver for AAT1290 current regulator 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=1411399340-16458-1-git-send-email-j.anaszewski@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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).