From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, sakari.ailus@iki.fi
Subject: Re: [PATCH v1] leds: Clarify supported chips by LM355x driver
Date: Fri, 26 Jan 2018 13:44:01 +0200 [thread overview]
Message-ID: <1516967041.7000.1282.camel@linux.intel.com> (raw)
In-Reply-To: <20180126102507.GA13775@amd>
On Fri, 2018-01-26 at 11:25 +0100, Pavel Machek wrote:
> On Fri 2018-01-26 09:38:28, Andy Shevchenko wrote:
> > LM3555 is supported by AS3645A.
> > Clarify this in Kconfig by referencing to AS3645A.
> >
> > No functional change.
> > This option enables support for LEDs connected to LM355x.
> > LM355x includes Torch, Flash and Indicator functions.
> >
> > + Note, LM3555 is driven by AS3645A.
> > +
>
> I took a look at the driver. It seems to me lm355x only handles lm3554
> and lm3556?
Correct.
> Perhaps Kconfig help should say that explicitely?
It's in the title.
> (I guess lm3555 is somehow different from the other two?)
Correct.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-01-26 11:44 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 [this message]
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
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=1516967041.7000.1282.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.