public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
	Ingi Kim <ingi2.kim@samsung.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
	Thierry Reding <treding@nvidia.com>,
	p.zabel@pengutronix.de, Andrew Lunn <andrew@lunn.ch>,
	Greg Kroah-Hartman <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" <devicetree@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	"sw0312.kim@samsung.com" <sw0312.kim@samsung.com>,
	ideal.song@samsung.com
Subject: Re: [PATCH 0/3] Add ktd2692 Flash LED driver
Date: Tue, 03 Mar 2015 08:48:01 +0100	[thread overview]
Message-ID: <54F56731.3050900@samsung.com> (raw)
In-Reply-To: <CAK5ve-JYixcO6F470wKZXDN-nkTfaRgmg7FBt1Y5O+tuznruwg@mail.gmail.com>

On 03/02/2015 09:07 PM, Bryan Wu wrote:
> On Mon, Mar 2, 2015 at 1:15 AM, Sakari Ailus <sakari.ailus@iki.fi> wrote:
>> H Ingi,
>>
>> On Mon, Mar 02, 2015 at 04:14:39PM +0900, Ingi Kim wrote:
>>> Hi Jacek
>>>
>>> On 2015년 02월 27일 17:42, Jacek Anaszewski wrote:
>>>> 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.
>>>>
>>>
>>> Ok, I'll check LED Flash class, and add torch-gpio
>>
>> Many LED flash chips include a hardware pin for torch control but few really
>> need it. If you don't, i.e. you can implement the torch using the control bus
>> instead, I think I'd probably drop it from the chip's DT bindings.
>>
>
> Ingi, please follow Jacek's advice to use LED Flash class interface.
> I'm reviewing those leds flash drivers and probably merge them soon.

Bryan please hold on with merging them as I am about to send new patch
set, as we've agreed that synchronized strobe feature should be removed
from the LED Flash class. There will be also some tweaking around
aat1290 DT bindings.

-- 
Best Regards,
Jacek Anaszewski

      parent reply	other threads:[~2015-03-03  7:48 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
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
2015-02-27  3:36   ` Varka Bhadram
2015-02-27  6:55     ` Ingi Kim
2015-02-27  8:42 ` [PATCH 0/3] Add ktd2692 Flash " Jacek Anaszewski
2015-03-02  7:14   ` Ingi Kim
2015-03-02  9:15     ` Sakari Ailus
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 [this message]

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=54F56731.3050900@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=ideal.song@samsung.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@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=sakari.ailus@iki.fi \
    --cc=sw0312.kim@samsung.com \
    --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