[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50e9aa50-99fb-0a1f-e395-c52bf91e8a7f@ti.com>
Date: Fri, 21 Sep 2018 07:44:00 -0500
From: Dan Murphy <dmurphy@...com>
To: Pavel Machek <pavel@....cz>
CC: Jacek Anaszewski <jacek.anaszewski@...il.com>,
<robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <lee.jones@...aro.org>,
<linux-omap@...r.kernel.org>, <linux-leds@...r.kernel.org>
Subject: Re: [PATCH v7 1/6] dt-bindings: ti-lmu: Remove LM3697
Pavel
On 09/20/2018 05:04 PM, Pavel Machek wrote:
> Hi!
>
>>>>> Easy to maintain will be a dedicated LED class driver.
>>>>
>>>> You mean, 3 dedicated LED class drivers and 3 MFD drivers with LED
>>>> parts? We'll need complex driver anyway, and I'd really like to have
>>>> just one.
>>>
>>> In the LED subsystem we can wrap common functionalities
>>> into a library object. MFD driver will be able to reuse it then.
>>
>> I am currently working on that code now. I expect a RFC on this this week.
>
> Looking forward to that.
>
> But you really need acks for the bindings, and since Rob is usually quite slow
> acking them, it is easiest to use the existing binding... if it is wrong it
> needs to be fixed, anyway.
>
OK I am in the midst of creating the code now. I have the common code done I just need to
make sure that it scales to other devices in the list.
The bindings will need to be updated to follow the LED bindings binding style.
I am wondering for the non-MFD parts if we should move the bindings to the LED
directory to make them easier to find.
Dan
> THanks,
>
> Pavel
>
--
------------------
Dan Murphy
Powered by blists - more mailing lists