From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Dan Murphy <dmurphy@ti.com>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: leds: Add bindings for lm3697 driver
Date: Mon, 10 Sep 2018 17:41:49 +0200 [thread overview]
Message-ID: <20180910154149.GA6845@amd> (raw)
In-Reply-To: <226b8770-7041-39a4-5a06-6002a7c1225f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Sat 2018-09-08 21:53:00, Jacek Anaszewski wrote:
> Dan,
>
> On 09/07/2018 03:52 PM, Dan Murphy wrote:
> [...]
> >>
> >>> And I think Jacek pointed out that the bindings references in this bindings
> >>> don't even exist.
> >>>
> >>> I am thinking we need to deprecate this MFD driver and consolidate these drivers
> >>> in the LED directory as we indicated before. I did not find any ti-lmu support
> >>> code.
> >>>
> >>> ti-lmu common core code and then the LED children appending the feature differentiation.
> >>
> >>> Need some maintainer weigh in here.
> >>
> >> Hehe. I'm maintnainer. Fun.
> >
> > I know. I want to see if there was any other opinion. Especially for the LED driver.
> >
> [...]
>
> I have a question - is this lm3697 LED controller a cell of some MFD
> device? Or is it a self-contained chip?
lm3697 is number for stand-alone device, but same hardware seems to be
embedded into multi-functional chips, with other numbers in lm36xx
series.
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 --]
prev parent reply other threads:[~2018-09-10 15:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 13:50 [PATCH v6 1/2] dt-bindings: leds: Add bindings for lm3697 driver Dan Murphy
2018-09-06 13:50 ` Dan Murphy
2018-09-06 13:50 ` [PATCH v6 2/2] leds: lm3697: Introduce the " Dan Murphy
2018-09-06 13:50 ` Dan Murphy
2018-09-06 21:16 ` [PATCH v6 1/2] dt-bindings: leds: Add bindings for " Pavel Machek
2018-09-07 13:20 ` Dan Murphy
2018-09-07 13:20 ` Dan Murphy
2018-09-07 13:32 ` Pavel Machek
2018-09-07 13:52 ` Dan Murphy
2018-09-07 13:52 ` Dan Murphy
2018-09-08 19:53 ` Jacek Anaszewski
2018-09-10 14:37 ` Dan Murphy
2018-09-10 14:37 ` Dan Murphy
2018-09-10 19:07 ` Jacek Anaszewski
2018-09-10 19:51 ` Dan Murphy
2018-09-10 19:51 ` Dan Murphy
2018-09-11 18:27 ` Jacek Anaszewski
2018-09-11 18:37 ` Dan Murphy
2018-09-11 18:37 ` Dan Murphy
2018-09-11 20:55 ` Pavel Machek
2018-09-11 21:05 ` Dan Murphy
2018-09-11 21:05 ` Dan Murphy
2018-09-10 15:41 ` Pavel Machek [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=20180910154149.GA6845@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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.