Linux Input/HID development
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Xavier Bestel <xav@bes.tel>, Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: lg-g15: Add support for the Logitech G710/G710+ gaming keyboards
Date: Fri, 15 May 2026 09:52:09 +0200	[thread overview]
Message-ID: <3a03ac01-3b82-4ad6-bd35-f91ce738847c@kernel.org> (raw)
In-Reply-To: <094db7d8-eb0c-4103-86fb-beb11580d53b@kernel.org>

Hi,

On 6-Apr-26 20:50, Hans de Goede wrote:
> Hi Xavier,
> 
> Thank you for your patch, it is always nice to have people helping
> with improving Linux support for devices like this.
> 
> On 2-Apr-26 09:52, Xavier Bestel wrote:
>> Add support for the Logitech G710 and G710+ (USB ID 046d:c24d) gaming
>> keyboards to the hid-lg-g15 driver.
>>
>> These keyboards have 6 G-keys (G1-G6), M-keys (M1-M3, MR), a game mode
>> toggle, and two independent backlights: one for the main keyboard and one
>> for the WASD keys, each with a physical button to cycle brightness through
>> 5 levels (0-4).
>>
>> Key implementation details:
>>
>>  - G-keys and M-keys are reported via HID input report 0x03 (4 bytes)
>>    using KEY_MACRO1-6, KEY_MACRO_PRESET1-3 and KEY_MACRO_RECORD_START.
>>
>>  - The WASD backlight LED is registered as
>>    "g15::kbd_zoned_backlight-wasd" rather than with a
>>    "::kbd_backlight" suffix, because UPower currently only supports a
>>    single kbd_backlight LED per device. This follows the nomenclature
>>    from Documentation/leds/leds-class.rst
> 
> Actually that nomenclature is something which was suggested in the past
> but has never been agreed upon.
> 
> Since the discussion about how to name the LED class devices for
> multi-zone keyboard backlights keeps coming up I've submitted a patch
> now to document how these should be named:
> 
> https://lore.kernel.org/linux-leds/20260406174638.320135-1-johannes.goede@oss.qualcomm.com/
> 
> Since the new userspace API for this needs to be agreed upon first, that
> patch should be accepted upstream first, before we can move forward with
> the G710 support from this patch.

My v2 patch with the LED naming scheme has been accepted into the
leds maintainer git tree now, so this is no longer a blocker for this
patch:

https://lore.kernel.org/linux-leds/20260504145434.12746-1-johannes.goede@oss.qualcomm.com/

Regards,

Hans




      reply	other threads:[~2026-05-15  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  7:52 [PATCH] HID: lg-g15: Add support for the Logitech G710/G710+ gaming keyboards Xavier Bestel
2026-04-04 10:05 ` Xavier Bestel
2026-04-04 10:07   ` Hans de Goede
2026-04-06 18:50 ` Hans de Goede
2026-05-15  7:52   ` Hans de Goede [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=3a03ac01-3b82-4ad6-bd35-f91ce738847c@kernel.org \
    --to=hansg@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xav@bes.tel \
    /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