On Wed, 28 Oct 2026 at 21:26, ZiAo Wang <[email protected]> wrote:
>
> Valkyrie USB LCD devices (0x345f:0x9132) expose a HID interface
> for vendor-specific display control commands and a separate USB
> interface for bulk framebuffer transfers.
>
> The HID interface is not intended for input and should be managed
> by the dedicated USB display driver instead of the HID subsystem.
>
> Add the device to the HID quirk table with HID_QUIRK_IGNORE to
> prevent the HID driver from binding to it.
>
> Signed-off-by: ZiAo Wang <[email protected]>
> ---
> drivers/hid/hid-ids.h | 3 +++
> drivers/hid/hid-quirks.c | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 91319aa651..d135ea8f06 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -1704,4 +1704,7 @@
> #define USB_VENDOR_ID_HUAWEI 0x12d1
> #define USB_DEVICE_ID_HUAWEI_CD30KBD 0x109b
>
> +#define USB_VENDOR_ID_VALKYRIE 0x345f
> +#define USB_PRODUCT_ID_VALKYRIE_LCD 0x9132
This VID and PID pair is used by all macrosilicon usb display adapters,
so it wouldn't just affect this product.
It also doesn't seem to negatively affect the device and is
useful for debugging, so I wouldn't recommend ignoring it.
> #endif
> diff --git a/drivers/hid/hid-quirks.c b/drivers/hid/hid-quirks.c
> index 793db001a6..70ada7320c 100644
> --- a/drivers/hid/hid-quirks.c
> +++ b/drivers/hid/hid-quirks.c
> @@ -226,6 +226,7 @@ static const struct hid_device_id hid_quirks[] = {
> { HID_USB_DEVICE(USB_VENDOR_ID_YJXCHIP, USB_DEVICE_ID_YJXCHIP_MOUSE),
> HID_QUIRK_ALWAYS_POLL },
> { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH,
> USB_DEVICE_ID_LOGITECH_GROUP_AUDIO), HID_QUIRK_NOGET },
> + { HID_USB_DEVICE(USB_VENDOR_ID_VALKYRIE,
> USB_PRODUCT_ID_VALKYRIE_LCD), HID_QUIRK_IGNORE },
>
> { 0 }
> };
> --
> 2.56.0
>
