[PATCH v5 0/3] Add Nsiway NS2009 resistive touchscreen support
From: Mizuno Miotsuki via B4 Relay
Date: Tue Oct 13 2026 - 18:48:45 EST
Add the Nsiway vendor prefix, hardware binding and standalone polling
input driver for the NS2009.
Changes since v4:
- Remove the review-attribution sentence from the binding commit message.
- Add Conor Dooley's Reviewed-by to the binding. No code changes.
Changes since v3:
- Require vdd-supply following Conor Dooley's review; keep vref-supply
optional, including for the 10-pin package without a VREF pin.
- Manage declared supplies over the input open/close lifecycle and retain
an outstanding enable reference if disabling fails.
- Use a named I2C device-ID initializer following the bot review.
- Preserve Conor's Acked-by on the unchanged vendor-prefix patch.
Tested on UNIHIKER M10 V1.2 with the real vcc_io regulator: touch, release,
dragging, open/close and inhibit/uninhibit passed. Tests used a validation
module and a temporary live-DT supply property; the final DTB has not been
booted. s2idle resume passed; deep wake remains unresolved.
TSC2007 reuse was investigated, but polling and raw-contact handling still
need separate policy and TI hardware regression coverage is outstanding.
The board DTS is a separate Rockchip series depending on this binding and
the previously submitted common I2C2 enablement.
Signed-off-by: Mizuno Miotsuki <founder@xxxxxxxxxxx>
---
Mizuno Miotsuki (3):
dt-bindings: vendor-prefixes: add Nsiway
dt-bindings: input: touchscreen: add Nsiway NS2009
Input: add Nsiway NS2009 resistive touchscreen driver
.../bindings/input/touchscreen/nsiway,ns2009.yaml | 79 +++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 7 +
drivers/input/touchscreen/Kconfig | 10 +
drivers/input/touchscreen/Makefile | 1 +
drivers/input/touchscreen/ns2009.c | 230 +++++++++++++++++++++
6 files changed, 329 insertions(+)
---
base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
change-id: 20261013-review-self-ns2009-v4-20261013-693ff98b425f
Best regards,
--
Mizuno Miotsuki <founder@xxxxxxxxxxx>