From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>, "Pavel Machek" <pavel@ucw.cz>,
"Dan Murphy" <dmurphy@ti.com>,
"Kate Stewart" <kstewart@linuxfoundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Enrico Weigelt" <info@metux.net>,
"Allison Randal" <allison@lohutok.net>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] leds: backlight: Register with class backlight
Date: Mon, 25 Nov 2019 19:19:32 +0100 [thread overview]
Message-ID: <056103e5-a26d-c6ea-15f2-0991d4f2721e@gmail.com> (raw)
In-Reply-To: <cover.1574692624.git.agx@sigxcpu.org>
Hi Guido,
You might want to check the pending patch set [0].
On 11/25/19 3:47 PM, Guido Günther wrote:
> When using current LCD drivers as ledtrig backlight they're
> not registered with the backlight device class. This has
> two problems: they're usually not found by userspace since
> these tools usually look in /sys/class/backlight and they
> can't be used as backlight phandles in device tree for
> e.g. LCD panels.
>
> This is an RFC if this is worthwhile at all? A current problem
> is that changing the LED brightness does currently not notify
> the class backlight so they can get out of sync but i could
> look into that if the approach makes sense.
>
>
> Guido Günther (1):
> leds: backlight: register with class backlight too
>
> drivers/leds/trigger/ledtrig-backlight.c | 54 ++++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
[0]
https://lore.kernel.org/linux-leds/20191007124437.20367-1-jjhiblot@ti.com/
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2019-11-25 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 14:47 [RFC PATCH 0/1] leds: backlight: Register with class backlight Guido Günther
2019-11-25 14:47 ` [RFC PATCH 1/1] leds: backlight: register with class backlight too Guido Günther
2019-11-25 18:19 ` Jacek Anaszewski [this message]
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=056103e5-a26d-c6ea-15f2-0991d4f2721e@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=agx@sigxcpu.org \
--cc=allison@lohutok.net \
--cc=dmurphy@ti.com \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
/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).