All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Carlos Ferreira <carlosmiguelferreira.2003@gmail.com>,
	ilpo.jarvinen@linux.intel.com, Pavel Machek <pavel@ucw.cz>,
	mustafa.eskieksi@gmail.com, platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Linux LED Subsystem <linux-leds@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] HP: wmi: Add documentation for the LED API naming scheme
Date: Fri, 16 Aug 2024 17:11:08 +0100	[thread overview]
Message-ID: <20240816161108.GE5853@google.com> (raw)
In-Reply-To: <7bf12e39-8956-4cd3-a90a-871291d84370@redhat.com>

On Mon, 12 Aug 2024, Hans de Goede wrote:

> Hi all,
> 
> +Cc Pavel, Lee, linux-leds for review by the linux LED subsystem folks.
> 
> Pavel, Lee there are 2 pdx86 drivers for control of zoned (3/4 zones)
> RGB backlit laptop keyboards pending:
> 
> https://lore.kernel.org/platform-driver-x86/20240719100011.16656-2-carlosmiguelferreira.2003@gmail.com/
> https://lore.kernel.org/platform-driver-x86/20240806205001.191551-2-mustafa.eskieksi@gmail.com/
> 
> both of these will use 1 multicolor LED class device per keyboard zone,
> using the naming convention documented in this patch.
> 
> It would be good if we can get feedback or an ack from you for this
> userspace API before merging these drivers.
> 
> Note the first part of the patch documents the already existing naming
> scheme for single zone (RGB or mono color) backlight keyboards. This
> scheme is already used by many drivers and by userspace consumers like
> upower. So this is just documenting existing userspace API which so far
> was not documented.
> 
> 
> Carlos, Thank you for writing this patch.
> 
> For v2 please change the patch subject to:
> 
> "Documentation: leds: leds-class: Add documentation for keyboard backlight LED device names"
> 
> and this should also be merged through the LED subsystem tree, so for v2
> please send this to Pavel + Lee with linux-leds + platform-driver-x86
> in the Cc.

Please use get_maintainer.pl when submitting patches:

  % ./scripts/get_maintainer.pl -f Documentation/leds/leds-class.rst
  Pavel Machek <pavel@ucw.cz> (maintainer:LED SUBSYSTEM)
  Lee Jones <lee@kernel.org> (maintainer:LED SUBSYSTEM)
  Jonathan Corbet <corbet@lwn.net> (maintainer:DOCUMENTATION)
  linux-leds@vger.kernel.org (open list:LED SUBSYSTEM)
  linux-doc@vger.kernel.org (open list:DOCUMENTATION)
  linux-kernel@vger.kernel.org (open list)

I'll review the patch once it's been submitted properly, thanks.

> On 7/19/24 11:59 AM, Carlos Ferreira wrote:
> > This patch adds documentation for the LED API class-device naming
> > scheme practice.
> >
> > Signed-off-by: Carlos Ferreira <carlosmiguelferreira.2003@gmail.com>
> > ---
> >  Documentation/leds/leds-class.rst | 40 +++++++++++++++++++++++++++++++
> >  1 file changed, 40 insertions(+)
> > 
> > diff --git a/Documentation/leds/leds-class.rst b/Documentation/leds/leds-class.rst
> > index 5db620ed27aa..8e74a436ca9b 100644
> > --- a/Documentation/leds/leds-class.rst
> > +++ b/Documentation/leds/leds-class.rst
> > @@ -116,6 +116,46 @@ above leaves scope for further attributes should they be needed. If sections
> >  of the name don't apply, just leave that section blank.
> >  
> >  
> > +Keyboard backlight control
> > +==========================
> > +
> > +For backlit keyboards with a single brightness / color settings a
> > +single (multicolor) LED device should be used to allow userspace
> > +to change the backlight brightness (and if possible the color).
> > +This LED device must have a name ending in ':kbd_backlight'.
> > +
> > +For RGB backlit keyboards with multiple control zones, one multicolor
> > +LED device should be used per zone. These LED devices' name
> > +must follow the following form:
> > +
> > +	"<devicename>:rgb:kbd_zoned_backlight-<zone_name>"
> > +
> > +and <devicename> must be the same for all zones of the same keyboard.
> > +
> > +Where possible <zone_name> should be a value already used by other
> > +zoned keyboards with a similar or identical zone layout, e.g.:
> > +
> > +<devicename>:rgb:kbd_zoned_backlight-right
> > +<devicename>:rgb:kbd_zoned_backlight-middle
> > +<devicename>:rgb:kbd_zoned_backlight-left
> > +<devicename>:rgb:kbd_zoned_backlight-corners
> 
> The -corners zone was based on a misunderstanding about
> the Excaliber laptop's functionality, please drop
> the "<devicename>:rgb:kbd_zoned_backlight-corners"
> line here as well as below.
> 
> Regards,
> 
> Hans
> 
> 
> 
> > +<devicename>:rgb:kbd_zoned_backlight-wasd
> > +
> > +or:
> > +
> > +<devicename>:rgb:kbd_zoned_backlight-main
> > +<devicename>:rgb:kbd_zoned_backlight-cursor
> > +<devicename>:rgb:kbd_zoned_backlight-numpad
> > +<devicename>:rgb:kbd_zoned_backlight-corners
> > +<devicename>:rgb:kbd_zoned_backlight-wasd
> > +
> > +Note that this is intended for keyboards with a limited number of zones,
> > +keyboards with per key addressable backlighting must not use LED
> > +class devices since the sysfs API is not suitable for rapidly change
> > +multiple LEDs in one "commit" as is necessary to do animations /
> > +special effects on such keyboards.
> > +
> > +
> >  Brightness setting API
> >  ======================
> >  
> 

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2024-08-16 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19  9:59 [PATCH v4 0/2] HP: wmi: added support for 4 zone keyboard rgb Carlos Ferreira
2024-07-19  9:59 ` [PATCH v4 1/2] " Carlos Ferreira
2024-07-25  3:40   ` kernel test robot
2024-08-12 13:17   ` Ilpo Järvinen
2024-08-12 13:44   ` Hans de Goede
2024-08-12 15:57     ` Ilpo Järvinen
2024-07-19  9:59 ` [PATCH v4 2/2] HP: wmi: Add documentation for the LED API naming scheme Carlos Ferreira
2024-08-12 12:48   ` Hans de Goede
2024-08-16 16:11     ` Lee Jones [this message]

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=20240816161108.GE5853@google.com \
    --to=lee@kernel.org \
    --cc=carlosmiguelferreira.2003@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mustafa.eskieksi@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.