From: Pavel Machek <pavel@ucw.cz>
To: Rishit Bansal <rishitbansal0@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>
Subject: Re: API for setting colors of RGB backlit keyboard zones (was [PATCH V3] platform/x86: hp-wmi: Support omen backlight control wmi-acpi methods)
Date: Sat, 18 Feb 2023 12:48:19 +0100 [thread overview]
Message-ID: <Y/C7A9eCjpdbzYbz@duo.ucw.cz> (raw)
In-Reply-To: <b11185d3-fbf3-a461-39bc-67bee4739e40@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Hi!
> > I do agree with you that we need to avoid kbd_backlight in the name to avoid causing existing upower code to have weird interactions with this (it supports / assumes there is only 1 kbd_backlight LED class device).
> >
> > So lets go with just these 4:
> >
> > /sys/class/leds/hp_omen::kbd_zoned_backlight-1/
> > /sys/class/leds/hp_omen::kbd_zoned_backlight-2/
> > /sys/class/leds/hp_omen::kbd_zoned_backlight-3/
> > /sys/class/leds/hp_omen::kbd_zoned_backlight-4/
> >
> > Using the _zoned_ between kbd and baclight to avoid confusing the existing upower code. Then once this has landed we can look into extending upower support for this.
> >
> > Note the requested documentation patch should probably also explain that the _zoned_ was done deliberately to make current upower code ignore the devices.
> >
>
> This makes sense, I agree that the global LED file will cause more confusion
> and hacks in the code. I'll start working on the _zoned_ naming scheme with
> 4 files + documentation changes and make a patch for this soon!
>
/sys/class/leds/:rgb:kbd_zoned_backlight-4/ is better than what was
suggested above. But we already use _1 suffix to deduplicate the, so
I'm not sure this is best naming.
There are keyboards with per-key backlight. How do you suggest to
solve those?
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-02-18 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230131235027.36304-1-rishitbansal0@gmail.com>
[not found] ` <9b761996-d522-b0f8-6472-10e40e09e036@redhat.com>
[not found] ` <65a11a89-e780-6d60-a40e-cd3245780762@gmail.com>
2023-02-02 12:43 ` [PATCH V3] platform/x86: hp-wmi: Support omen backlight control wmi-acpi methods Hans de Goede
2023-02-02 19:59 ` Rishit Bansal
2023-02-06 14:32 ` API for setting colors of RGB backlit keyboard zones (was [PATCH V3] platform/x86: hp-wmi: Support omen backlight control wmi-acpi methods) Hans de Goede
2023-02-06 15:07 ` Rishit Bansal
2023-02-07 11:53 ` Pavel Machek
2023-02-07 13:05 ` Rishit Bansal
2023-02-13 12:49 ` Hans de Goede
2023-02-13 14:16 ` Rishit Bansal
2023-02-18 11:48 ` Pavel Machek [this message]
2023-02-19 13:20 ` Hans de Goede
2023-02-19 18:46 ` Rishit Bansal
2023-02-20 8:43 ` Hans de Goede
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=Y/C7A9eCjpdbzYbz@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rishitbansal0@gmail.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