From: Werner Sembach <wse@tuxedocomputers.com>
To: Armin Wolf <W_Armin@gmx.de>, linux-leds@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>, Lee Jones <lee@kernel.org>,
pavel@kernel.org
Subject: Re: Maximum values for multi_intensity sysfs attribute
Date: Tue, 3 Mar 2026 21:43:31 +0100 [thread overview]
Message-ID: <5a82f282-2ab6-4fa9-82fa-a38fdd99c386@tuxedocomputers.com> (raw)
In-Reply-To: <c3b283c5-0433-4c2b-92cf-30dcfab5e0e9@tuxedocomputers.com>
Am 03.03.26 um 21:35 schrieb Werner Sembach:
>
> Am 03.03.26 um 21:11 schrieb Armin Wolf:
>> Am 14.02.26 um 20:15 schrieb Armin Wolf:
>>
>>> Hello,
>>>
>>> i am currently adding support for RGB keyboard backlight control to the
>>> uniwill-laptop
>>> driver, and want to use the multicolor LED class for that. However the
>>> hardware interface
>>> is a bit exotic:
>>>
>>> - 5 global brightness levels
>>> - 50 intensity levels for each R/G/B channel
>>>
>>> I am now asking myself how this should be mapped onto the multi_intensity
>>> sysfs attribute.
>>> Should i set max_brightness to 5 and reject intensity values larger that 50?
>>> Or should
>>> i set max_brightness to 50 and interpolate? What is the input range of
>>> intensity values?
>>>
>>> Thanks,
>>> Armin Wolf
>>
>> Any ideas on this? My current approach would be to use 5 for the max
>> brightness and clamp intensity
>> values to 50.
> Another idea is to have multi_intensity values 0-255 and then map it to the
> closest color so normal rgb values can be passed
this would also offer a hook point for some scaling: some uniwill devices have a
noticeable color hue like pinkish or greenish because the leds max brightness is
not well balanced, in tuxedo-drivers we sometimes apply some adjustments
regulating 1 or 2 of the colors generally down like 5 or 10%
>>
>> Thanks,
>> Armin Wolf
>>
next prev parent reply other threads:[~2026-03-03 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 19:15 Armin Wolf
2026-03-03 20:11 ` Armin Wolf
2026-03-03 20:35 ` Werner Sembach
2026-03-03 20:43 ` Werner Sembach [this message]
2026-03-04 11:45 ` Pőcze Barnabás
2026-03-04 11:58 ` Werner Sembach
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=5a82f282-2ab6-4fa9-82fa-a38fdd99c386@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=W_Armin@gmx.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
/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®