From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Marek Behun <marek.behun@nic.cz>
Cc: Pavel Machek <pavel@ucw.cz>, linux-leds@vger.kernel.org
Subject: Re: [PATCH RFC leds-next] leds: initial support for Turris Omnia LEDs
Date: Sat, 28 Mar 2020 14:01:47 +0100 [thread overview]
Message-ID: <00b6737b-47f8-7ea4-74b7-eee3d2aefdf3@gmail.com> (raw)
In-Reply-To: <20200328133629.79603fe3@nic.cz>
Hi Marek,
On 3/28/20 1:36 PM, Marek Behun wrote:
>> This was only RFC, please do not merge.
>
> Jacek, Pavel,
>
> I decided to abandon the microcontroller driver path.
> But nonetheless there is still one thing I would like to solve.
>
> The front button on Omnia is used to control the global brightness of
> the RGB LEDs, so that user can change it if the LEDs glow too much.
> The microcontroller does this as such: there is another PWM on top of
> all the LED PWMs, and this value can be manipulated via the same i2c
> interface as the LEDs, but via another command.
>
> The thing is that I would like to somehow export this global brightness
> setting to userspace, because otherwise it gets reset after reboot, and
> I want the user to be able to set this global brightness by software,
> so that they won't have to change it after every reboot manually by
> pressing the front button.
>
> I am wondering how to do this. Last year I proposed this by adding a
> sysfs attribute file to the device which is parent to the LEDs, but you
> did not agree :(
I already proposed adding a "luma" LED class device for similar
case [0], but didn't here any feedback from Pavel so far.
[0]
https://lore.kernel.org/linux-leds/1583502010-16210-1-git-send-email-nbelin@baylibre.com/T/#mf52c8d4f68260a445223c26957c61e6267e0932d
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2020-03-28 13:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 18:16 [PATCH RFC leds-next] leds: initial support for Turris Omnia LEDs Marek Behún
2020-03-21 15:33 ` Pavel Machek
2020-03-28 12:08 ` Jacek Anaszewski
2020-03-28 12:27 ` Marek Behun
2020-03-28 12:36 ` Marek Behun
2020-03-28 13:01 ` Jacek Anaszewski [this message]
2020-03-28 17:20 ` Marek Behun
2020-03-29 12:53 ` Jacek Anaszewski
2020-04-02 14:29 ` Marek Behun
2020-04-02 20:19 ` Jacek Anaszewski
2020-04-02 20:57 ` Marek Behun
2020-04-02 21:00 ` Jacek Anaszewski
2020-04-06 21:10 ` Pavel Machek
2020-04-06 21:08 ` Pavel Machek
2020-04-06 20:42 ` Pavel Machek
2020-03-21 15:34 ` Pavel Machek
2020-03-21 18:01 ` Jacek Anaszewski
2020-03-21 20:50 ` Marek Behun
2020-03-22 15:51 ` Jacek Anaszewski
2020-04-06 8:34 ` Pavel Machek
2020-04-06 13:53 ` Marek Behun
2020-03-21 18:55 ` Jacek Anaszewski
2020-03-21 20:44 ` Marek Behun
2020-03-22 15:28 ` Jacek Anaszewski
2020-03-21 21:53 ` Marek Behun
2020-03-21 22:16 ` Pavel Machek
2020-03-21 22:36 ` Marek Behun
2020-03-22 15:50 ` Dan Murphy
2020-04-06 8:40 ` 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=00b6737b-47f8-7ea4-74b7-eee3d2aefdf3@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--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