From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Jean-Jacques Hiblot <jjhiblot@ti.com>,
devicetree@vger.kernel.org, pavel@ucw.cz,
linux-leds@vger.kernel.org, robh@kernel.org, "Valkeinen,
Tomi" <tomi.valkeinen@ti.com>
Subject: Re: devicetree bindings for a generic led-based backlight driver
Date: Wed, 26 Jun 2019 20:55:37 +0200 [thread overview]
Message-ID: <400ac00b-d3c7-b58f-52fa-8b18b6c7e4a2@gmail.com> (raw)
In-Reply-To: <69f3a300-9e37-448d-e6fa-49c1c9ca0dd6@ti.com>
Hi Jean,
On 6/26/19 5:34 PM, Jean-Jacques Hiblot wrote:
> Hi,
>
> A few years ago (2015), Tomi Valkeinen posted a series implementing a
> backlight driver on top of a LED device.
>
> https://patchwork.kernel.org/patch/7293991/
> https://patchwork.kernel.org/patch/7294001/
> https://patchwork.kernel.org/patch/7293981/
>
> The discussion stopped because he lacked the time to work on it.
>
> I will be taking over the task and, before heading in the wrong
> direction, wanted a confirmation that the binding Tomi last proposed in
> hist last email was indeed the preferred option.
>
> It will probably require some modifications in the LED core to create
> the right kind of led-device (normal, flash or backlight) based on the
> compatible option.
I recall that discussion. I gave my ack for the LED changes but
now we have more LED people that might want to look into that.
Regarding the bindings we have pending LED naming patch set,
that deprecates DT label property [0] and introduces standardized
LED functions.
[0] https://lkml.org/lkml/2019/6/9/728
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-06-26 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 15:34 devicetree bindings for a generic led-based backlight driver Jean-Jacques Hiblot
2019-06-26 18:55 ` Jacek Anaszewski [this message]
2019-06-27 13:14 ` Jean-Jacques Hiblot
2019-06-27 20:19 ` Jacek Anaszewski
2019-07-06 15:19 ` Pavel Machek
2019-07-10 9:26 ` Jean-Jacques Hiblot
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=400ac00b-d3c7-b58f-52fa-8b18b6c7e4a2@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jjhiblot@ti.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=tomi.valkeinen@ti.com \
/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).