From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: [PATCH] leds: add TI LMU backlight driver
Date: Thu, 30 Aug 2018 21:20:18 +0200 [thread overview]
Message-ID: <c72eb0ff-b54c-4670-580c-e31625b3c275@gmail.com> (raw)
In-Reply-To: <20180830082219.GA10133@amd>
Hi Pavel,
Thank you for the patch.
Looking for DT bindings I can find the following
Documentation/devicetree/bindings/mfd/ti-lmu.txt,
which for LED bindings redirects to:
"[2] ../leds/leds-lm3633.txt",
but it is not present in the mainline.
Best regards,
Jacek Anaszewski
On 08/30/2018 10:22 AM, Pavel Machek wrote:
>
> This adds backlight support for the following TI LMU
> chips: LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
>
> It controls LEDs on Droid 4
> smartphone, including keyboard and screen backlights.
>
> Signed-off-by: Milo Kim <milo.kim@ti.com>
> [add LED subsystem support for keyboard backlight and rework DT
> binding according to Rob Herrings feedback]
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
> [remove backlight subsystem support for now]
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
[...]
next prev parent reply other threads:[~2018-08-30 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 21:20 [rfc] leds: add TI LMU backlight driver Pavel Machek
2018-08-30 8:22 ` [PATCH] " Pavel Machek
2018-08-30 16:40 ` Tony Lindgren
2018-08-30 19:20 ` Jacek Anaszewski [this message]
2018-08-30 19:41 ` [rfc] " Dan Murphy
2018-08-30 20:18 ` Pavel Machek
2018-08-31 12:19 ` Dan Murphy
2018-08-31 21:30 ` Pavel Machek
2018-09-04 14:34 ` Dan Murphy
2018-09-06 10:16 ` Pavel Machek
2018-08-30 20:37 ` kbuild test robot
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=c72eb0ff-b54c-4670-580c-e31625b3c275@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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).