public inbox for linux-leds@vger.kernel.org
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: linux-leds@vger.kernel.org, Werner Sembach <wse@tuxedocomputers.com>
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:11:41 +0100	[thread overview]
Message-ID: <2b5fa1b7-9d97-4f9b-b03e-6ecfa74c63ab@gmx.de> (raw)
In-Reply-To: <2d91a44e-fce2-42dc-b529-133ab4a191f0@gmx.de>

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.

Thanks,
Armin Wolf


  reply	other threads:[~2026-03-03 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 19:15 Maximum values for multi_intensity sysfs attribute Armin Wolf
2026-03-03 20:11 ` Armin Wolf [this message]
2026-03-03 20:35   ` Werner Sembach
2026-03-03 20:43     ` Werner Sembach
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=2b5fa1b7-9d97-4f9b-b03e-6ecfa74c63ab@gmx.de \
    --to=w_armin@gmx.de \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=wse@tuxedocomputers.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