Re: [PATCH v3] Input: synaptics - support the touchpad LED on RMI function $30
From: Dmitry Torokhov
Date: Sun Nov 15 2026 - 23:41:55 EST
Hi Ahmad,
On Sat, Nov 14, 2026 at 12:38:08PM +0330, ahmad baghereslami wrote:
> Some HP laptops have an LED in the top left corner of the Synaptics
> touchpad that HP's Windows driver lights while the touchpad is disabled
> (double tap on that corner). On the HP ZBook 17 G3 (SYN3040, TM2706-002)
> the LED is not driven through the PS/2 deluxe LED command: the Windows
> driver (SynTP.sys 19.0.19.68) switches the touchpad to RMI register
> access over PS/2 with mode byte 0x7f, looks up function $30 (GPIO/LED)
> in the page description table and sets the LED bit in its control
> register:
>
> register write: SetScale 2:1, SetRate <reg>, SetRate <value>
> register read: SetScale 2:1, SetRate <reg>, GetInfo (first byte)
>
> For touchpads in a new rmi_led_pnp_ids list, look up the F30 LED this
> way when the touchpad is set up and register a
> synaptics::touchpad_disabled LED class device.
Why is this touchpad running in legacy PS/2 mode instead of native RMI4
mode over SMBus (InterTouch / rmi4_smbus)?
Could you please check if booting with psmouse.synaptics_intertouch=1
switches the touchpad (and the pointing stick via F03) to RMI4 over
SMBus on the HP ZBook 17 G3?
If InterTouch works on this machine, we should add "SYN3040" to
smbus_pnp_ids[] in drivers/input/mouse/synaptics.c and implement LED
class support in drivers/input/rmi4/rmi_f30.c (which already parses
f30->has_led and the F30 control register layout), rather than adding
RMI4 PDT scanning and F30 register manipulation over the PS/2 command
backdoor in the legacy PS/2 driver.
Thanks.
--
Dmitry