From: Conor Dooley <conor@kernel.org>
To: Jizhou Tong <fqwqf@fqwqf.xyz>
Cc: Jingyuan Liang <jingyliang@chromium.org>,
jikos@kernel.org, bentiss@kernel.org, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
daleyo@gmail.com, broonie@kernel.org,
u.kleine-koenig@baylibre.com, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [RFC PATCH v2 4/6] dt-bindings: input: describe the Romulus13 QSPI touchpad
Date: Wed, 28 Oct 2026 17:58:30 +0000 [thread overview]
Message-ID: <20261028-punctured-flagpole-c7ec4cfc4609@spud> (raw)
In-Reply-To: <010601a1334e2298-73816c42-ca83-40fe-9c7a-e771c466a4e6-000000@ap-northeast-1.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 3476 bytes --]
On Tue, Oct 13, 2026 at 03:28:41AM +0000, Jizhou Tong wrote:
> Describe the fixed-address HID-over-SPI touchpad on Surface Laptop 7
> 13.8-inch, with quad address/data transfers, an active-low reset and a 5
> V supply.
>
> Signed-off-by: Jizhou Tong <fqwqf@fqwqf.xyz>
With the changes to the hid-over-spi series that this is based on, can
this device now go into hid-over-spi.yaml?
> ---
> .../input/microsoft,romulus13-touchpad.yaml | 86 +++++++++++++++++++
> 1 file changed, 86 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/microsoft,romulus13-touchpad.yaml
>
> diff --git a/Documentation/devicetree/bindings/input/microsoft,romulus13-touchpad.yaml b/Documentation/devicetree/bindings/input/microsoft,romulus13-touchpad.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..88e4664c56e7fb1c3f9f5949a3ded2f9d7070604
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/microsoft,romulus13-touchpad.yaml
> @@ -0,0 +1,86 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/microsoft,romulus13-touchpad.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microsoft Surface Laptop 7 13.8-inch QSPI touchpad
> +
> +maintainers:
> + - Jizhou Tong <fqwqf@fqwqf.xyz>
> +
> +description:
> + The touchpad on the 13.8-inch Surface Laptop 7 uses the HID SPI v3
> + protocol over a quad SPI connection. Its supply and board reset states
> + must be controlled during initialization and recovery.
> +
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: microsoft,romulus13-touchpad
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + vdd-supply:
> + description: Touchpad 5 V supply.
> +
> + spi-max-frequency:
> + maximum: 20000000
> +
> + spi-rx-bus-width:
> + items:
> + - const: 4
> +
> + spi-tx-bus-width:
> + items:
> + - const: 4
> +
> + reset-gpios:
> + maxItems: 1
> + description: Active-low touchpad reset.
> +
> + pinctrl-0: true
> +
> + pinctrl-names:
> + items:
> + - const: default
Are these even something that needs to be added? I am pretty sure pinctrl
stuff is allowed in all nodes without being cited explicitly.
Looks okay to me other than these two things.
pw-bot: changes-requested
Thanks,
Conor.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - vdd-supply
> + - spi-rx-bus-width
> + - spi-tx-bus-width
> + - reset-gpios
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/gpio/gpio.h>
> +
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + touchpad@0 {
> + compatible = "microsoft,romulus13-touchpad";
> + reg = <0>;
> + spi-max-frequency = <20000000>;
> + spi-rx-bus-width = <4>;
> + spi-tx-bus-width = <4>;
> + interrupts-extended = <&tlmm 3 IRQ_TYPE_LEVEL_LOW>;
> + vdd-supply = <&vreg_ts_5p0>;
> + reset-gpios = <&tlmm 120 GPIO_ACTIVE_LOW>;
> + pinctrl-0 = <&touchpad_reset>;
> + pinctrl-names = "default";
> + };
> + };
> --
> 2.53.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-28 17:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 22:25 [PATCH v5 00/11] Add spi-hid transport driver Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 01/11] Documentation: Correction in HID output_report callback description Jingyuan Liang
2026-10-09 22:29 ` sashiko-bot
2026-10-13 20:49 ` Jingyuan Liang
2026-10-12 6:04 ` Krzysztof Kozlowski
2026-10-13 20:49 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 02/11] HID: Add BUS_SPI support and define HID_SPI_DEVICE macro Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 03/11] HID: spi-hid: add transport driver skeleton for HID over SPI bus Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 04/11] HID: spi-hid: add spi-hid driver HID layer Jingyuan Liang
2026-10-09 22:42 ` sashiko-bot
2026-10-13 21:21 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 05/11] HID: spi-hid: add HID SPI protocol implementation Jingyuan Liang
2026-10-09 22:42 ` sashiko-bot
2026-10-13 22:07 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 06/11] HID: spi-hid: add spi_hid traces Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 07/11] HID: spi-hid: add ACPI support for HID over SPI Jingyuan Liang
2026-10-09 22:41 ` sashiko-bot
2026-10-13 22:15 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 08/11] HID: spi-hid: add device tree " Jingyuan Liang
2026-10-12 12:49 ` Uwe Kleine-König
2026-10-13 22:26 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 09/11] dt-bindings: input: Document hid-over-spi DT schema Jingyuan Liang
2026-10-12 6:05 ` Krzysztof Kozlowski
2026-10-13 22:28 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 10/11] HID: spi-hid: add power management implementation Jingyuan Liang
2026-10-09 22:43 ` sashiko-bot
2026-10-13 22:57 ` Jingyuan Liang
2026-10-09 22:25 ` [PATCH v5 11/11] HID: spi-hid: add panel follower support Jingyuan Liang
2026-10-09 22:36 ` sashiko-bot
2026-10-13 23:06 ` Jingyuan Liang
2026-10-10 16:57 ` [PATCH 0/2] HID: spi-hid: handle reset assertion and resume handshake failures fQwQf
2026-10-13 2:54 ` [PATCH v2 " Jizhou Tong
2026-10-13 3:11 ` [PATCH v2 1/2] HID: spi-hid: propagate reset assertion errors during initialization Jizhou Tong
2026-10-13 3:11 ` [PATCH v2 2/2] HID: spi-hid: report a missing reset handshake on resume Jizhou Tong
2026-11-05 19:01 ` [PATCH v3 0/2] HID: spi-hid: propagate reset GPIO errors Jizhou Tong
2026-11-05 19:15 ` [PATCH v3 1/2] HID: spi-hid: propagate reset assertion errors during initialization Jizhou Tong
2026-11-05 19:15 ` [PATCH v3 2/2] HID: spi-hid: propagate reset GPIO errors from resume Jizhou Tong
2026-10-10 16:57 ` [RFC PATCH 0/6] HID: spi-hid: add Romulus13 quad-SPI support on v5 fQwQf
2026-10-13 3:13 ` [RFC PATCH v2 " Jizhou Tong
2026-10-13 3:28 ` [RFC PATCH v2 1/6] HID: spi-hid: isolate DMA transfers from protocol buffers Jizhou Tong
2026-10-13 3:28 ` [RFC PATCH v2 2/6] HID: spi-hid: add spi-mem quad-SPI transfers Jizhou Tong
2026-10-13 3:28 ` [RFC PATCH v2 3/6] HID: spi-hid: assemble bounded fragmented input reports Jizhou Tong
2026-10-13 3:28 ` [RFC PATCH v2 4/6] dt-bindings: input: describe the Romulus13 QSPI touchpad Jizhou Tong
2026-10-28 17:58 ` Conor Dooley [this message]
2026-10-13 3:28 ` [RFC PATCH v2 5/6] HID: spi-hid: support " Jizhou Tong
2026-10-13 3:28 ` [RFC PATCH v2 6/6] HID: spi-hid: expose readiness for reset diagnostics Jizhou Tong
2026-11-05 19:19 ` [RFC PATCH v3 0/5] HID: spi-hid: add quad-SPI support for Romulus13 Jizhou Tong
2026-11-05 19:22 ` [RFC PATCH v3 1/5] HID: spi-hid: isolate DMA transfers from protocol buffers Jizhou Tong
2026-11-05 19:33 ` sashiko-bot
2026-11-06 16:32 ` Jizhou Tong
2026-11-05 19:23 ` [RFC PATCH v3 2/5] HID: spi-hid: add spi-mem quad-SPI transfers Jizhou Tong
2026-11-05 19:23 ` [RFC PATCH v3 3/5] HID: spi-hid: assemble bounded fragmented input reports Jizhou Tong
2026-11-05 19:23 ` [RFC PATCH v3 4/5] dt-bindings: input: hid-over-spi: add the Surface Laptop 7 touchpad Jizhou Tong
2026-11-06 17:43 ` Conor Dooley
2026-11-05 19:23 ` [RFC PATCH v3 5/5] HID: spi-hid: support the Romulus13 QSPI touchpad Jizhou Tong
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=20261028-punctured-flagpole-c7ec4cfc4609@spud \
--to=conor@kernel.org \
--cc=bentiss@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daleyo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fqwqf@fqwqf.xyz \
--cc=jikos@kernel.org \
--cc=jingyliang@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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 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.