From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, javier@dowhile0.org,
jacek.anaszewski@gmail.com
Subject: Re: [PATCH v3 2/3] leds: as3645a: Add LED flash class driver
Date: Thu, 7 Sep 2017 14:50:27 +0200 [thread overview]
Message-ID: <20170907125027.GA3108@amd> (raw)
In-Reply-To: <20170907102657.stoqw5e7glbkbz2z@valkosipuli.retiisi.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
Hi!
> On Mon, Aug 28, 2017 at 01:04:51PM +0200, Pavel Machek wrote:
> > On Wed 2017-08-23 11:10:59, Sakari Ailus wrote:
> > > Add a LED flash class driver for the as3654a flash controller. A V4L2 flash
> > > driver for it already exists (drivers/media/i2c/as3645a.c), and this driver
> > > is based on that.
> >
> > We do not want to have two drivers for same hardware... how is that
> > supposed to work?
>
> No, we don't. The intent is to remove the other driver later on, as it's
> implemented as a V4L2 sub-device driver. It also lacks DT support.
Could we perhaps remove the driver with the same patch that merges
this?
Having two drivers would be confusing.
> > Yes, we might want to have both LED and v4l2 interface for a single
> > LED, because v4l2 is just too hairy to use, but we should not
> > duplicate drivers for that.
> >
> > We _might_ want to do some helpers; as these LED drivers are all quite
> > similar, it should be possible to have "flash led driver" and just
> > link it to v4l2 and LED interfaces...
>
> This is what the new LED (flash) class driver does. Feature-wise it's a
> superset of the old one. There's a minor matter left, though, which is
> querying the flash strobe status which the old driver did and the new one
> does not do yet. I don't know if anyone ever even used that feature though.
Yes, I don't think anyone will notice...
Anyway,
Acked-by: Pavel Machek <pavel@ucw.cz>
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-09-07 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:10 [PATCH v3 0/3] AS3645A flash support Sakari Ailus
2017-08-23 8:10 ` [PATCH v3 1/3] dt: bindings: Document DT bindings for Analog devices as3645a Sakari Ailus
2017-08-28 11:00 ` Pavel Machek
2017-08-23 8:10 ` [PATCH v3 2/3] leds: as3645a: Add LED flash class driver Sakari Ailus
[not found] ` <20170823081100.11733-3-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-08-28 11:04 ` Pavel Machek
2017-09-07 10:26 ` Sakari Ailus
2017-09-07 12:50 ` Pavel Machek [this message]
2017-09-07 14:52 ` Sakari Ailus
2017-09-07 20:17 ` Pavel Machek
2017-08-23 8:11 ` [PATCH v3 3/3] arm: dts: omap3: N9/N950: Add AS3645A camera flash Sakari Ailus
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=20170907125027.GA3108@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).