From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH v1] leds: Clarify supported chips by LM355x driver
Date: Tue, 30 Jan 2018 13:08:20 +0200 [thread overview]
Message-ID: <1517310500.7000.1319.camel@linux.intel.com> (raw)
In-Reply-To: <5968dfb2-8bf9-917f-4299-47bf1cd97124@gmail.com>
On Mon, 2018-01-29 at 21:46 +0100, Jacek Anaszewski wrote:
> On 01/28/2018 03:30 PM, Andy Shevchenko wrote:
> > On Fri, 2018-01-26 at 21:39 +0100, Jacek Anaszewski wrote:
> > > On 01/26/2018 08:38 AM, Andy Shevchenko wrote:
> > > > + Note, LM3555 is driven by AS3645A.
> > >
> > > Could you please provide more details on this relationship?
> > > Looking at the datasheet it seems that both chips are standalone
> > > and controlled via I2C and/or via GPIO in case of LM3555.
> >
> > The only difference I see looking in datasheets again that AS3645A
> > supports dual-led mode, by using STROBE signal in case of parallel
> > interface or thru additional bits in I2C mode.
> >
> > Can you be more specific what exactly makes you feel that they are
> > not
> > compatible?
>
> The expression "LM3555 is driven by AS3645A" brings on mind rather
> some type of hardware dependency between chips than drivers
> similarity.
>
> Now I understand that you meant that both devices can be driven by any
> of leds-lm355x or leds-as3645a driver, am I right?
No. The chip in question is LM3555, and it's handled only in as3645a
driver.
> I suspected that I got something entirely wrong here, especially
> that both you and Pavel agreed.
>
> But, given that it turned out that leds-lm355x.c doesn't support
> LM3555 and its documentation [3] indeed shows the affinity with
> AS3645, I suppose that this patch is a result of a premature
> conclusion drawn basing on the driver's description rather than its
> capabilities.
>
> [3] http://www.ti.com/lit/ds/symlink/lm3555.pdf
>
> Effectively, the only sensible change seems to be:
>
> - tristate "LED support for LM355x Chips, LM3554 and LM3556"
> + tristate "LED support for LM3554 and LM3556 chips"
> depends on LEDS_CLASS && I2C
> select REGMAP_I2C
> help
> - This option enables support for LEDs connected to LM355x.
> - LM355x includes Torch, Flash and Indicator functions.
> + This option enables support for LEDs connected to LM3554
> + and LM3556. It includes Torch, Flash and Indicator
> functions.
I like patch Pavel sent previously. It feels more comprehensive than
this one.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-01-30 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:38 [PATCH v1] leds: Clarify supported chips by LM355x driver Andy Shevchenko
2018-01-26 10:25 ` Pavel Machek
2018-01-26 11:44 ` Andy Shevchenko
2018-01-26 21:05 ` Pavel Machek
2018-01-26 21:32 ` Pavel Machek
2018-01-26 22:07 ` Sakari Ailus
2018-01-28 14:18 ` Andy Shevchenko
2018-01-26 20:39 ` Jacek Anaszewski
2018-01-28 14:30 ` Andy Shevchenko
2018-01-29 20:46 ` Jacek Anaszewski
2018-01-30 11:08 ` Andy Shevchenko [this message]
2018-01-30 20:04 ` Jacek Anaszewski
2018-02-01 20:26 ` [PATCH v2] " Pavel Machek
2018-02-01 21:33 ` 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=1517310500.7000.1319.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--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