devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Ingi Kim <ingi2.kim@samsung.com>
Cc: robh+dt@kerner.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	cooloney@gmail.com, rpurdie@rpsys.net, treding@nvidia.com,
	p.zabel@pengutronix.de, andrew@lunn.ch,
	gregkh@linuxfoundation.org, florian.vaussard@epfl.ch,
	arno@natisbad.org, kuninori.morimoto.gx@renesas.com,
	hytszk@gmail.com, antonynpavlov@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH 0/3] Add ktd2692 Flash LED driver
Date: Fri, 27 Feb 2015 09:42:29 +0100	[thread overview]
Message-ID: <54F02DF5.1000706@samsung.com> (raw)
In-Reply-To: <1424998891-25591-1-git-send-email-ingi2.kim@samsung.com>

Hi Ingi,

On 02/27/2015 02:01 AM, Ingi Kim wrote:
> This patch supports KTD2692 flash LED driver
>
> Ingi Kim (3):
>    of: Add vendor prefix for Kinetic technologies
>    leds: ktd2692: add device tree bindings for ktd2692
>    leds: Add ktd2692 flash LED driver
>
>   .../devicetree/bindings/leds/leds-ktd2692.txt      |   19 ++
>   .../devicetree/bindings/vendor-prefixes.txt        |    1 +
>   drivers/leds/Kconfig                               |    8 +
>   drivers/leds/Makefile                              |    1 +
>   drivers/leds/leds-ktd2692.c                        |  245 ++++++++++++++++++++
>   5 files changed, 274 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/leds/leds-ktd2692.txt
>   create mode 100644 drivers/leds/leds-ktd2692.c
>

In your device tree binding documentation there is torch-gpio mentioned,
but you seem not to use it in the driver.

We have already LED Flash class (/drivers/leds/led-class-flash.c) for
this type of devices, which handles both torch and flash modes
(flash_strobe sysfs attribute is provided for strobing the flash).

The reference drivers using LED Flash class are still pending [1], but I
think that at least leds-aat1290 driver is almost ready for merging.
It controls very similar device to yours.

Another advantage of using LED Flash class is that it has been designed
to be compatible with Video for Linux 2 subsystem, which will allow for 
registering LED Flash class devices as a V4L2 sub-devices.

Adding Sakari.

-- 
Best Regards,
Jacek Anaszewski

[1] http://www.spinics.net/lists/linux-media/msg86632.html

  parent reply	other threads:[~2015-02-27  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  1:01 [PATCH 0/3] Add ktd2692 Flash LED driver Ingi Kim
     [not found] ` <1424998891-25591-1-git-send-email-ingi2.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-02-27  1:01   ` [PATCH 1/3] of: Add vendor prefix for Kinetic technologies Ingi Kim
2015-02-27  1:01 ` [PATCH 2/3] leds: ktd2692: add device tree bindings for ktd2692 Ingi Kim
2015-02-27  1:01 ` [PATCH 3/3] leds: Add ktd2692 flash LED driver Ingi Kim
     [not found]   ` <1424998891-25591-4-git-send-email-ingi2.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-02-27  3:36     ` Varka Bhadram
2015-02-27  6:55       ` Ingi Kim
2015-02-27  8:42 ` Jacek Anaszewski [this message]
2015-03-02  7:14   ` [PATCH 0/3] Add ktd2692 Flash " Ingi Kim
2015-03-02  9:15     ` Sakari Ailus
     [not found]       ` <20150302091530.GQ6539-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2015-03-02 20:07         ` Bryan Wu
2015-03-02 22:03           ` Sakari Ailus
2015-03-03  2:55             ` Ingi Kim
2015-03-03  7:48           ` 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=54F02DF5.1000706@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=andrew@lunn.ch \
    --cc=antonynpavlov@gmail.com \
    --cc=arno@natisbad.org \
    --cc=cooloney@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.vaussard@epfl.ch \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hytszk@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ingi2.kim@samsung.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kerner.org \
    --cc=rpurdie@rpsys.net \
    --cc=sakari.ailus@iki.fi \
    --cc=treding@nvidia.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).