From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Dan Murphy <dmurphy@ti.com>, Pavel Machek <pavel@ucw.cz>
Cc: 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: Sat, 8 Sep 2018 21:53:00 +0200 [thread overview]
Message-ID: <226b8770-7041-39a4-5a06-6002a7c1225f@gmail.com> (raw)
In-Reply-To: <70f7506c-6a3d-3830-59a4-a246dc6163f7@ti.com>
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?
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-09-08 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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:32 ` Pavel Machek
2018-09-07 13:52 ` Dan Murphy
2018-09-08 19:53 ` Jacek Anaszewski [this message]
2018-09-10 14:37 ` Dan Murphy
2018-09-10 19:07 ` Jacek Anaszewski
2018-09-10 19:51 ` Dan Murphy
2018-09-11 18:27 ` Jacek Anaszewski
2018-09-11 18:37 ` Dan Murphy
2018-09-11 20:55 ` Pavel Machek
2018-09-11 21:05 ` Dan Murphy
2018-09-10 15:41 ` Pavel Machek
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=226b8770-7041-39a4-5a06-6002a7c1225f@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®