Linux Input/HID development
 help / color / mirror / Atom feed
From: Benjamin Tissoires <bentiss@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: synonym <20000l@pm.me>,
	 "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"luke@ljones.dev" <luke@ljones.dev>,
	 "benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>
Subject: Re: ASUS T302CHI keyboard dock (0b05:182f) missing from hid-asus, brightness keys dead
Date: Fri, 16 Oct 2026 15:48:47 +0200	[thread overview]
Message-ID: <atIq520WDeOgyAJD@beelink> (raw)
In-Reply-To: <o1392s9p-6rrq-3179-289p-447n1703pp1p@xreary.bet>

On Oct 16 2026, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.com>

You are missing a proper title, and FWIW, b4 doesn't recognize this as a
patch.

> 
> synonym reports: "The dock (USB 0b05:182f) reports brightness on the ASUS
> vendor usage page 0xff31, usages 0x10 and 0x20, which hid-asus already maps to
> KEY_BRIGHTNESSDOWN / KEY_BRIGHTNESSUP. Because the device is not in
> asus_devices[], it is claimed by hid-generic, which ignores the vendor page
> entirely, so Fn+F5 and Fn+F6 produce no input events at all - not even a
> scancode. Keys on the standard consumer page (volume) on the same device work
> fine, which makes this look like a backlight or ACPI problem rather than a HID
> one."
> 
> Add the device ID.
> 
> Reported-by: synonym <20000l@pm.me>
> Signed-off-by: Jiri Kosina <jkosina@suse.com>

Anyway, feel free to push it to for-7.4/hid-asus with my:

Acked-by: Benjamin Tissoires <bentiss@kernel.org>

Cheers,
Benjamin

> ---
>  drivers/hid/hid-asus.c | 2 ++
>  drivers/hid/hid-ids.h  | 1 +
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/hid/hid-asus.c b/drivers/hid/hid-asus.c
> index ec966fc0a411..42655a6d59d9 100644
> --- a/drivers/hid/hid-asus.c
> +++ b/drivers/hid/hid-asus.c
> @@ -1733,6 +1733,8 @@ static const struct hid_device_id asus_devices[] = {
>  	  QUIRK_USE_KBD_BACKLIGHT | QUIRK_ROG_NKEY_KEYBOARD },
>  	{ HID_DEVICE(BUS_USB, HID_GROUP_GENERIC,
>  		USB_VENDOR_ID_ASUSTEK, USB_DEVICE_ID_ASUSTEK_T101HA_KEYBOARD) },
> +	{ HID_DEVICE(BUS_USB, HID_GROUP_GENERIC,
> +		USB_VENDOR_ID_ASUSTEK, USB_DEVICE_ID_ASUSTEK_T302CHI_KEYBOARD) },
>  	{ }
>  };
>  MODULE_DEVICE_TABLE(hid, asus_devices);
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 43bbddf84e61..63d69d49ee50 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -218,6 +218,7 @@
>  #define USB_DEVICE_ID_ASUSTEK_T100TAF_KEYBOARD	0x1807
>  #define USB_DEVICE_ID_ASUSTEK_T100CHI_KEYBOARD	0x8502
>  #define USB_DEVICE_ID_ASUSTEK_T101HA_KEYBOARD	0x183d
> +#define USB_DEVICE_ID_ASUSTEK_T302CHI_KEYBOARD	0x182f
>  #define USB_DEVICE_ID_ASUSTEK_T304_KEYBOARD	0x184a
>  #define USB_DEVICE_ID_ASUSTEK_I2C_KEYBOARD	0x8585
>  #define USB_DEVICE_ID_ASUSTEK_I2C_ZENBOOK_KEYBOARD	0x4b42
> 
> -- 
> Jiri Kosina
> SUSE Labs
> 
> 

  reply	other threads:[~2026-10-16 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OCupKvK8JTzwwSrGfH05iZGTNOuUCg3cPoiTlNgdDUUt24LbtaNYWciyGx1C90egfE2C8EdnANX7sXM6IwBh5xfycQNq-ji_xAuNLRAVvQQ=@pm.me>
2026-10-16 13:06 ` ASUS T302CHI keyboard dock (0b05:182f) missing from hid-asus, brightness keys dead Jiri Kosina
2026-10-16 13:48   ` Benjamin Tissoires [this message]
2026-09-07 22:11 dontfindmymail

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=atIq520WDeOgyAJD@beelink \
    --to=bentiss@kernel.org \
    --cc=20000l@pm.me \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=luke@ljones.dev \
    /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