linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: robh+dt@kernel.org
Cc: Dan Murphy <dmurphy@ti.com>,
	pavel@ucw.cz, lee.jones@linaro.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 4/6] dt-bindings: ti-lmu: Modify dt bindings for the LM3697
Date: Fri, 12 Apr 2019 21:34:33 +0200	[thread overview]
Message-ID: <1a1482f7-a683-49d5-69a3-aa73a641288e@gmail.com> (raw)
In-Reply-To: <04e160da-a73e-d330-3df4-8f420b3612b4@gmail.com>

And one more:

[5] - LED naming patch set v3

On 4/11/19 9:48 PM, Jacek Anaszewski wrote:
> Hi Rob,
> 
> I've collected references to the DT patches we're waiting
> to be reviewed. This is just to make sure that none of them
> will be missed - recent traffic on the linux-leds list
> is a bit heavier.
> 
> [0] - draft of LED multi color class - we would especially like
>        to get a feedback on the proposed brightness-model DT design
> [1][2] - LM3697 backlight driver rework
> [3][4] - LM36274 backlight driver with regulator support
> 
> On 4/5/19 4:28 PM, Dan Murphy wrote:
>> The LM3697 is a single function LED driver. The single function LED
>> driver needs to reside in the LED directory as a dedicated LED driver
>> and not as a MFD device.  The device does have common brightness and ramp
>> features and those can be accomodated by a TI LMU framework.
>>
>> The LM3697 dt binding needs to be moved from the ti-lmu.txt and a 
>> dedicated
>> LED dt binding needs to be added.  The new LM3697 LED dt binding will 
>> then
>> reside in the Documentation/devicetree/bindings/leds directory and 
>> follow the
>> current LED and general bindings guidelines.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
[...]
> [0] https://marc.info/?l=linux-kernel&m=155414072611538&w=2
> [1] https://marc.info/?l=devicetree&m=155447454524411&w=2
> [2] https://lore.kernel.org/patchwork/patch/1058762/
> [3] https://marc.info/?l=devicetree&m=155447624324995&w=2
> [4] https://lore.kernel.org/patchwork/patch/1058779/
> 

[5] - https://marc.info/?l=linux-kernel&m=155405492231039&w=2

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2019-04-12 19:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 14:28 [PATCH v2 1/6] dt-bindings: mfd: LMU: Add the ramp up/down property Dan Murphy
2019-04-05 14:28 ` [PATCH v2 2/6] dt-bindings: mfd: LMU: Add ti,brightness-resolution Dan Murphy
2019-04-29 17:33   ` Rob Herring
2019-04-05 14:28 ` [PATCH v2 3/6] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-04-05 14:28 ` [PATCH v2 4/6] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-04-11 19:48   ` Jacek Anaszewski
2019-04-12 19:34     ` Jacek Anaszewski [this message]
2019-04-24 19:24       ` Dan Murphy
2019-04-29 17:34   ` Rob Herring
2019-04-05 14:28 ` [PATCH v2 5/6] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-04-05 14:28 ` [PATCH v2 6/6] leds: lm3697: Introduce the lm3697 driver Dan Murphy
2019-04-29 17:32 ` [PATCH v2 1/6] dt-bindings: mfd: LMU: Add the ramp up/down property Rob Herring

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=1a1482f7-a683-49d5-69a3-aa73a641288e@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=lee.jones@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).