From: Bastien Nocera <hadess@hadess.net>
To: Stuart Hayhurst <stuart.a.hayhurst@gmail.com>,
linux-kernel@vger.kernel.org, Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Filipe Laíns" <lains@riseup.net>
Subject: Re: [PATCH] HID: logitech-hidpp: Add support for G502 X Plus USB mouse
Date: Mon, 27 Jul 2026 15:00:07 +0200 [thread overview]
Message-ID: <ca28c348b95fdabc19ea86ab56716e0cbbae24ad.camel@hadess.net> (raw)
In-Reply-To: <20260721171246.461232-5-stuart.a.hayhurst@gmail.com>
On Tue, 2026-07-21 at 18:12 +0100, Stuart Hayhurst wrote:
> The wireless dongle is already supported, this adds detection for
> the mouse in wired mode. Supports battery reporting.
>
> Signed-off-by: Stuart Hayhurst <stuart.a.hayhurst@gmail.com>
Reviewed-by: Bastien Nocera <hadess@hadess.net>
> ---
> drivers/hid/hid-logitech-hidpp.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-
> logitech-hidpp.c
> index 90b0184df777..25620494e741 100644
> --- a/drivers/hid/hid-logitech-hidpp.c
> +++ b/drivers/hid/hid-logitech-hidpp.c
> @@ -4647,6 +4647,8 @@ static const struct hid_device_id
> hidpp_devices[] = {
> HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC082) },
> { /* Logitech G502 Lightspeed Wireless Gaming Mouse over USB
> */
> HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC08D) },
> + { /* Logitech G502 X Plus Wireless Gaming Mouse over USB */
> + HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC095) },
> { /* Logitech G703 Gaming Mouse over USB */
> HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xC087) },
> { /* Logitech G703 Hero Gaming Mouse over USB */
prev parent reply other threads:[~2026-07-27 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 17:12 [PATCH] HID: logitech-hidpp: Add support for G502 X Plus USB mouse Stuart Hayhurst
2026-07-27 13:00 ` Bastien Nocera [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=ca28c348b95fdabc19ea86ab56716e0cbbae24ad.camel@hadess.net \
--to=hadess@hadess.net \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.a.hayhurst@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