All of lore.kernel.org
 help / color / mirror / Atom feed
From: ahmad baghereslami <ahmad.b1995@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Input: synaptics - support the touchpad LED on RMI function $30
Date: Mon, 16 Nov 2026 10:49:06 +0330	[thread overview]
Message-ID: <20261116071906.30110-1-ahmad.b1995@gmail.com> (raw)
In-Reply-To: <7f9d0adf1f49c5a2b3919130caf0acb7@gmail.com>

Hi Dmitry,

On Mon, Nov 16, 2026 at 04:41:48AM +0000, Dmitry Torokhov wrote:
> 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?

Yes, it does. With psmouse.synaptics_intertouch=1 the touchpad binds as
"Synaptics TM2706-002" through rmi4_smbus, and motion, taps, buttons,
scrolling and the pointing stick (F03) all work.

The reason I kept it on PS/2 is a side effect on this laptop: the
embedded controller turns the keyboard backlight back on when it sees
PS/2 input after the backlight has timed out. Over SMBus the touchpad's
traffic no longer passes through the EC, so touching the touchpad no
longer wakes the keyboard backlight; only typing does. Nothing else
differed in daily use.

If you still prefer the RMI4 route, I can send a series that adds
"SYN3040" to smbus_pnp_ids[] and implements LED class support in
rmi_f30.c, and drop the PS/2 backdoor. Or, if the backlight behaviour
is a reason to keep this touchpad on PS/2, I would keep the current
approach. Which would you prefer?

(Separately, sashiko found that v3 can leave the LED lit when a trigger
is removed at unbind; I have a fix ready for whichever version comes
next.)

Thanks,
Ahmad

      reply	other threads:[~2026-11-16  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  7:08 [PATCH] Input: synaptics - support the touchpad LED on RMI function $30 ahmad baghereslami
2026-10-30  7:24 ` sashiko-bot
2026-10-31  1:23 ` kernel test robot
2026-10-31  2:29 ` kernel test robot
2026-11-06  9:56 ` [PATCH v2] " ahmad baghereslami
2026-11-06 10:14   ` sashiko-bot
2026-11-14  9:08   ` [PATCH v3] " ahmad baghereslami
2026-11-14  9:24     ` sashiko-bot
2026-11-15 14:20       ` ahmad baghereslami
2026-11-16  4:41     ` Dmitry Torokhov
2026-11-16  7:19       ` ahmad baghereslami [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=20261116071906.30110-1-ahmad.b1995@gmail.com \
    --to=ahmad.b1995@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.