From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linux-leds@vger.kernel.org, linux-media@vger.kernel.org
Cc: devicetree@vger.kernel.org, kyungmin.park@samsung.com,
pavel@ucw.cz, cooloney@gmail.com, rpurdie@rpsys.net,
sakari.ailus@iki.fi, s.nawrocki@samsung.com,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: [PATCH v2 00/11] LED / flash API integration
Date: Fri, 27 Mar 2015 14:49:34 +0100 [thread overview]
Message-ID: <1427464185-27950-1-git-send-email-j.anaszewski@samsung.com> (raw)
This is a second non-RFC version of LED / flash API integration
series [1]. It is based on linux-next_20150327.
================
Changes since v1
================
- excluded exynos4-is media device related patches, as there is
consenus required related to flash devices handling in media device
DT bindings
- modifications around LED Flash class settings and v4l2 flash config
initialization in LED Flash class drivers and v4l2-flash wrapper
- switched to using DT node name as a device name for leds-max77693
and leds-aat1290 drivers, in case DT 'label' property is absent
- dropped OF dependecy for v4l2-flash wrapper
- moved LED_FAULTS definitions from led-class-flash.h to uapi/linux/leds.h
- allowed for multiple clients of v4l2-flash sub-device
======================
Changes since RFC v13:
======================
- reduced number of patches - some of them have been merged
- slightly modified max77693-led device naming
- fixed issues in v4l2-flash helpers detected with yavta
- cleaned up AAT1290 device tree documentation
- added GPIOLIB dependecy to AAT1290 related entry in Kconfig
Thanks,
Jacek Anaszewski
[1] http://www.spinics.net/lists/kernel/msg1944538.html
Jacek Anaszewski (11):
leds: unify the location of led-trigger API
leds: add uapi header file
leds: Add support for max77693 mfd flash cell
DT: Add documentation for the mfd Maxim max77693
leds: Add driver for AAT1290 flash LED controller
of: Add Skyworks Solutions, Inc. vendor prefix
DT: Add documentation for the Skyworks AAT1290
media: Add registration helpers for V4L2 flash sub-devices
Documentation: leds: Add description of v4l2-flash sub-device
leds: max77693: add support for V4L2 Flash sub-device
leds: aat1290: add support for V4L2 Flash sub-device
.../devicetree/bindings/leds/leds-aat1290.txt | 70 ++
Documentation/devicetree/bindings/mfd/max77693.txt | 61 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
Documentation/leds/leds-class-flash.txt | 13 +
drivers/leds/Kconfig | 19 +
drivers/leds/Makefile | 2 +
drivers/leds/leds-aat1290.c | 518 ++++++++++
drivers/leds/leds-max77693.c | 1086 ++++++++++++++++++++
drivers/leds/leds.h | 24 -
drivers/media/v4l2-core/Kconfig | 11 +
drivers/media/v4l2-core/Makefile | 2 +
drivers/media/v4l2-core/v4l2-flash.c | 619 +++++++++++
include/linux/led-class-flash.h | 16 +-
include/linux/leds.h | 24 +
include/media/v4l2-flash.h | 144 +++
include/uapi/linux/leds.h | 34 +
16 files changed, 2605 insertions(+), 39 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/leds-aat1290.txt
create mode 100644 drivers/leds/leds-aat1290.c
create mode 100644 drivers/leds/leds-max77693.c
create mode 100644 drivers/media/v4l2-core/v4l2-flash.c
create mode 100644 include/media/v4l2-flash.h
create mode 100644 include/uapi/linux/leds.h
--
1.7.9.5
next reply other threads:[~2015-03-27 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 13:49 Jacek Anaszewski [this message]
2015-03-27 13:49 ` [PATCH v2 01/11] leds: unify the location of led-trigger API Jacek Anaszewski
2015-03-28 22:33 ` Sakari Ailus
2015-03-27 13:49 ` [PATCH v2 02/11] leds: add uapi header file Jacek Anaszewski
[not found] ` <1427464185-27950-3-git-send-email-j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-28 22:35 ` Sakari Ailus
2015-03-30 7:22 ` Jacek Anaszewski
2015-03-27 13:49 ` [PATCH v2 03/11] leds: Add support for max77693 mfd flash cell Jacek Anaszewski
2015-03-28 22:45 ` Sakari Ailus
2015-03-27 13:49 ` [PATCH v2 04/11] DT: Add documentation for the mfd Maxim max77693 Jacek Anaszewski
2015-03-27 14:06 ` Jacek Anaszewski
2015-03-28 22:55 ` Sakari Ailus
2015-03-30 7:36 ` Jacek Anaszewski
[not found] ` <5518FD05.5060800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-30 9:35 ` Sakari Ailus
2015-03-27 13:49 ` [PATCH v2 05/11] leds: Add driver for AAT1290 flash LED controller Jacek Anaszewski
2015-03-28 22:57 ` Sakari Ailus
2015-03-27 13:49 ` [PATCH v2 06/11] of: Add Skyworks Solutions, Inc. vendor prefix Jacek Anaszewski
[not found] ` <1427464185-27950-1-git-send-email-j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-27 13:49 ` [PATCH v2 07/11] DT: Add documentation for the Skyworks AAT1290 Jacek Anaszewski
2015-03-27 13:49 ` [PATCH v2 08/11] media: Add registration helpers for V4L2 flash sub-devices Jacek Anaszewski
2015-03-27 13:49 ` [PATCH v2 09/11] Documentation: leds: Add description of v4l2-flash sub-device Jacek Anaszewski
2015-03-28 23:35 ` Sakari Ailus
2015-03-27 13:49 ` [PATCH v2 10/11] leds: max77693: add support for V4L2 Flash sub-device Jacek Anaszewski
2015-03-27 13:49 ` [PATCH v2 11/11] leds: aat1290: " 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=1427464185-27950-1-git-send-email-j.anaszewski@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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