From: Emfox Zhou <emfox@debian.org>
To: Even Xu <even.xu@intel.com>, Xinpeng Sun <xinpeng.sun@intel.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/5] HID: intel-thc-hid: intel-ipts: support THC IPTS ports
Date: Wed, 18 Nov 2026 13:39:59 +0800 [thread overview]
Message-ID: <20261118054004.363766-1-emfox@debian.org> (raw)
The THC ports on Tiger Lake, Lakefield, Alder Lake and Raptor Lake run in
IPTS mode: plain SPI with a private framing instead of HIDSPI, which is
all intel-thc-hid handles today. This adds a backend for them next to
intel-quickspi and intel-quicki2c, on top of the same core.
It is based on v7.4-rc3 with two core fix series applied, both still
under review:
https://lore.kernel.org/r/20261118053132.253448-1-emfox@debian.org
https://lore.kernel.org/r/20261117105420.318995-1-emfox@debian.org
One gives the DMA engines a lifetime, the other keeps a PRD table from
overrunning after a reset, and the recovery path here relies on both.
They overlap in intel-thc-dma.c: apply the first, then the second.
Register, DMA and interrupt work goes through the exported intel-thc API,
except in four places where the core has no call for it: the reset,
port-supported and quiesce-state bits of THC_M_PRT_CONTROL are accessed
directly. Nothing outside the new directory changes except Kconfig and
Makefile.
The hardware facts - port IDs, configuration block layout, frame codes and
header sizes - come from the ithc driver linux-surface ships, at
https://github.com/quo/ithc-linux 6d53c9c (dual licensed GPL-2.0 /
BSD-2-Clause); no code is taken from it. The layout, the frame format and
the ordering between quiesce, interrupt configuration and the DMA engines
are the parts most likely to need scrutiny; each is argued in the commit
message that relies on it. All of it was confirmed on a Surface Pro 8 with
a 045e:0c37 controller.
The first four patches each leave a state that builds and loads: port
bring-up, DMA and interrupts, HID registration, system sleep. The fifth
documents the frame format and the IPTS handshake.
Link to v6: https://lore.kernel.org/r/20261117073554.11557-1-emfox@debian.org
Changes in v7:
- A reset no longer races the threaded handler: the port is masked,
synchronize_irq() waits for a run already inside, and only then is the
engine reset. A run that acknowledged the end of a frame the reset had
just re-armed the engine for would lose the interrupt announcing it
again. The two flags are cleared in an order that cannot turn away a
run which found the reset finished.
- A request that cannot complete is refused instead of sent: one issued
from inside the threaded handler, which is the thread that has to
deliver its completion, and one issued while a reset is queued or
running, where the write would wait out its timeout holding the bus
lock the reset needs. The descriptor path retries both a reset's
refusal and a write that lost its completion to one, since a
descriptor request carries nothing a late answer could spoil.
- The waits happen outside the lock, which now covers only the write.
The handler calls into the HID core on its way to a report, so a
request issued there would wait for a lock its own thread holds. A
queued reset leaves the line open for the same reason, and reports an
overrun once instead of once per frame.
- The feature gate is released by the caller that takes the answer, not
by the frame that brings it, and the check and the copy happen under
one lock hold. Only a timeout shuts the channel: an answer dropped by
a reset was never left out there.
- The port is masked before the interrupt handler is registered, so an
enable left by firmware cannot make the shared level line assert with
nothing to acknowledge it. Teardown keeps the line open until the
write already inside thc_dma_write() gets its completion, and waits
for the handler once more after the buffers are gone.
- Smaller ones: a descriptor larger than HID_MAX_DESCRIPTOR_SIZE is
rejected before it reaches hid_parse_report(); the SPI timing comment
says fastest, not slowest; the DEVRST comment says which way the bit
goes; the two comments that disagreed about masking are one.
- The documentation names the two steps that precede the first
configuration read, gives the bit positions it had only described in
words, points at ipts.h for the offsets it restates, and says what
system sleep does to the hidraw node.
Emfox Zhou (5):
HID: intel-thc-hid: intel-ipts: bring up the port
HID: intel-thc-hid: intel-ipts: receive reports
HID: intel-thc-hid: intel-ipts: add the HID device
HID: intel-thc-hid: intel-ipts: handle system sleep
HID: intel-thc-hid: intel-ipts: document the IPTS mode
Documentation/hid/intel-thc-hid.rst | 109 +-
drivers/hid/intel-thc-hid/Kconfig | 14 +
drivers/hid/intel-thc-hid/Makefile | 4 +
drivers/hid/intel-thc-hid/intel-ipts/ipts.c | 975 ++++++++++++++++++
drivers/hid/intel-thc-hid/intel-ipts/ipts.h | 200 ++++
.../hid/intel-thc-hid/intel-ipts/pci-ipts.c | 193 ++++
6 files changed, 1494 insertions(+), 1 deletion(-)
create mode 100644 drivers/hid/intel-thc-hid/intel-ipts/ipts.c
create mode 100644 drivers/hid/intel-thc-hid/intel-ipts/ipts.h
create mode 100644 drivers/hid/intel-thc-hid/intel-ipts/pci-ipts.c
base-commit: aebb7274476403040d582c61478df8f4a7bf9cd3
next reply other threads:[~2026-11-18 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 5:39 Emfox Zhou [this message]
2026-11-18 5:40 ` [PATCH v7 1/5] HID: intel-thc-hid: intel-ipts: bring up the port Emfox Zhou
2026-11-18 5:40 ` [PATCH v7 2/5] HID: intel-thc-hid: intel-ipts: receive reports Emfox Zhou
2026-11-18 5:40 ` [PATCH v7 3/5] HID: intel-thc-hid: intel-ipts: add the HID device Emfox Zhou
2026-11-18 5:40 ` [PATCH v7 4/5] HID: intel-thc-hid: intel-ipts: handle system sleep Emfox Zhou
2026-11-18 5:40 ` [PATCH v7 5/5] HID: intel-thc-hid: intel-ipts: document the IPTS mode Emfox Zhou
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=20261118054004.363766-1-emfox@debian.org \
--to=emfox@debian.org \
--cc=bentiss@kernel.org \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xinpeng.sun@intel.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
all inboxes | Powered by JetHome®