Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Evan Lawrence <development@laserology.net>
Cc: linux-input@vger.kernel.org, linux-api@vger.kernel.org,
	 miroslav.bendik@gmail.com
Subject: Re: [PATCH v5] Input: synaptics - add pass-through mode for TrackPoint
Date: Fri, 14 Aug 2026 12:13:22 -0700	[thread overview]
Message-ID: <an9ocXI6b7WEI8D2@google.com> (raw)
In-Reply-To: <20260810142440.9060-1-development@laserology.net>

Hi Evan,

On Mon, Aug 10, 2026 at 02:25:03PM +0000, Evan Lawrence wrote:
> Synaptics touchpads with a pass-through port (PS/2 guest) default to
> encapsulating guest data in the touchpad's own packets, limiting the
> guest device (typically a TrackPoint) to the touchpad's low poll rate.
> Enabling transparent pass-through mode tells the touchpad to stop
> generating its own packets and relay the raw byte stream from the guest
> directly, letting the TrackPoint run at its full native speed while the
> touchpad is effectively disabled.
> 
> This reworks an earlier implementation by Miroslav Bendík from 2022
> that was never merged. It keeps the same hardware-mode approach but
> commits the mode flag only after a successful mode command, moves the
> reconnect handling into a generic psmouse hook instead of protocol-
> specific checks in psmouse-interrupt, and documents the interface.
> 
> The mode is exposed via a sysfs transparent_mode attribute that allows
> userspace to switch between full-rate TrackPoint and full-rate touchpad
> operation at runtime.
> 
> If the system warm-boots while transparent mode is active the touchpad
> stays in that mode and does not acknowledge command bytes, so
> ps2_command() hangs and the device fails to be detected.  Escape
> transparent mode by writing SETSCALE21 + SETSCALE11 directly to the wire
> with serio_write() before attempting a reset or probe, both during
> initial detection and on reconnect.

I have not looked at the implementation yet, just a high-level question:

What devices need this? Can they work in SMbus/RMI4 mode instead (which
should alleviate bandwidth concerns)?

Thanks.

-- 
Dmitry

      parent reply	other threads:[~2026-08-14 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 14:25 [PATCH v5] Input: synaptics - add pass-through mode for TrackPoint Evan Lawrence
2026-08-10 14:45 ` sashiko-bot
2026-08-14 19:13 ` Dmitry Torokhov [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=an9ocXI6b7WEI8D2@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=development@laserology.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=miroslav.bendik@gmail.com \
    /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