Re: [PATCH] HID: asus: add new Asus EC hid device for keyboard backlight and FN HotKeys

[Alexandru Serdeliuc]

Hi Jiri,

Thanks for the feedback! No problem at all, December is always a busy
time of year, and there was no rush on this anyway.

I am going to test integrating the logic into hid-asus locally first on
the Zenbook A14 to confirm everything builds and functions properly on
this platform (aarch64).

Once I verify that it works as expected, I will report back and send
over a v2 patch series.

Thanks,
Alexandru



On 7/1/26 16:12, Jiri Kosina wrote:
> On Tue, 30 Jun 2026, Alexandru Serdeliuc wrote:
>
> > Hi Jiri, Benjamin,
> >
> > Enquiring if anyone has had a chance to look over this patch series from
> > December?
> >
> > To provide a bit of architectural context, this is a 100% pure HID client
> > driver.
> >
> > This laptop (Asus Zenbook A14 UX3407QA) runs on the Qualcomm ARM64 Snapdragon
> > platform.
> >
> > Because it is an ARM device, it does not use traditional legacy x86 ACPI/WMI
> > code.
> >
> > Instead, the Fn hotkeys and keyboard backlight controls are routed completely
> > through standard vendor-specific HID reports (using Report ID 0x5A) over the
> > existing I2C-HID transport layer.
> >
> > It requires absolutely zero Device Tree modifications or external platform
> > subsystem hooks to bind or function.
> >
> > The driver matches strictly on Vendor/Product ID (0x0B05 / 0x0220) passed
> > directly through the core HID subsystem.
> >
> > I would highly appreciate any architectural feedback or a quick review!
>
> Hi Alexandru,
>
> first - sorry for not having handled this, it somehow fell in between
> cracks.
>
> I have just one question -- wouldn't it be better to have this device
> handled as part of generic hid-asus driver? Giving too many Kconfig
> configurations for every specific model feels a little bit too
> overwhelming.
>
> (yes, we'd need to have hid-asus depend on I2C ... I don't think that's a
> big issue).
>
> Thanks, and sorry again,