[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20a814ce-a4c5-0649-6677-6b85a5fd2321@ti.com>
Date: Mon, 10 Sep 2018 09:37:15 -0500
From: Dan Murphy <dmurphy@...com>
To: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>
CC: <robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-leds@...r.kernel.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: leds: Add bindings for lm3697 driver
Jacek
On 09/08/2018 02:53 PM, 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?
>
This is a self contained chip. And the LM3697 only function is a LED driver.
It does not have any other special functions like the LM363X drivers for GPIO and Regulator support.
Dan
--
------------------
Dan Murphy
Powered by blists - more mailing lists