From: "Guido Günther" <agx@sigxcpu.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Camera LED on Librem 5 was Re: [PATCH] backlight: add led-backlight driver
Date: Fri, 14 Aug 2020 19:23:20 +0200 [thread overview]
Message-ID: <20200814172320.GA740513@bogon.m.sigxcpu.org> (raw)
In-Reply-To: <20200220234151.GB1544@amd>
Hi Pavel,
On Fri, Feb 21, 2020 at 12:41:51AM +0100, Pavel Machek wrote:
> Hi!
>
> > > This patch adds a led-backlight driver (led_bl), which is similar to
> > > pwm_bl except the driver uses a LED class driver to adjust the
> > > brightness in the HW. Multiple LEDs can be used for a single backlight.
> >
> > Tested-by: Guido Günther <agx@sigxcpu.org>
>
> Thanks for testing!
>
> I noticed blog post about using Librem 5 torch. Unfortunately, it used
> very strange/non-standard interface, first using LED as a GPIO to
> enable LED controller, then direct i2c access. That is not acceptable
> interface for mainline, and it would be better not to advertise such
> code, as it will likely become broken in future.
I agree, there's a driver for the lm3560 in media/ but how would one
expose the torch part as a LED? It seems you hit something similar in
https://lkml.org/lkml/2018/5/6/30
I also couldn't find an in tree driver that registers a flashlight
as a v4l subdev. Did i miss that?
Cheers,
-- Guido
next prev parent reply other threads:[~2020-08-14 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:14 Pavel Machek
2020-02-19 19:45 ` Tony Lindgren
2020-02-19 20:53 ` Pavel Machek
2020-02-19 21:15 ` Tony Lindgren
2020-02-19 23:54 ` Pavel Machek
2020-02-19 23:44 ` Sebastian Reichel
2020-02-20 14:54 ` Tony Lindgren
2020-02-20 7:48 ` Lee Jones
2020-02-20 15:09 ` Tony Lindgren
2020-02-20 8:29 ` Guido Günther
2020-02-20 23:41 ` Camera LED on Librem 5 was " Pavel Machek
2020-08-14 17:23 ` Guido Günther [this message]
2020-08-23 21:22 ` Pavel Machek
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=20200814172320.GA740513@bogon.m.sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®