mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miotsuki Mizuno <founder@crepuse.com>
To: "heiko@sntech.de" <heiko@sntech.de>
Cc: "conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"robh@kernel.org" <robh@kernel.org>
Subject: [PATCH] arm64: dts: rockchip: Enable touchscreen on UNIHIKER M10 V1.2
Date: Sat, 10 Oct 2026 23:29:10 +0000	[thread overview]
Message-ID: <20261010232908.26968-1-founder@crepuse.com> (raw)

Describe the onboard NS2009 resistive touchscreen at I2C2 address 0x48.
Use the tested inverted Y direction and raw Z1 contact threshold of 150.
Retain the native 12-bit ADC coordinate range.

The I2C2 controller is enabled by a separate board preparation patch.
This device node is independent of the display binding and DTS changes,
and depends on the separately submitted NS2009 binding and driver.

Link: https://lore.kernel.org/r/20261009144729.85832-1-founder@crepuse.com
Signed-off-by: Mizuno Miotsuki <founder@crepuse.com>
---

This board patch depends on the common I2C2 preparation commit and the
separately submitted NS2009 vendor-prefix/binding series. Those NS2009
dependencies are not in the pinned Rockchip tree; only the validation
branch imports them unchanged. The display series has no such dependency.
The prerequisite I2C2 board patch was submitted separately:
https://lore.kernel.org/r/20261010232831.26908-1-founder@crepuse.com

Validation: native DTS build passed, but native dt-validate -m reports
an unmatched NS2009 compatible. With submitted dependencies, target
CHECK_DTBS=y, direct dt-validate and binding example checks passed.
The exact combined DTB booted normally; the tester confirmed touch
direction and operation. Capture: nine down/up pairs, 208 frames, no
SYN_DROPPED, final released. One E0 ff ff invalid sample (-EIO) was
recorded; this is disclosed for review of the pending NS2009 support.
Deep suspend and calibrated five-point coverage are not claimed.

 arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
index 0c03f118378a..7ae3cc8a86e0 100644
--- a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
@@ -134,6 +134,13 @@ &emmc {
 &i2c2 {
 	clock-frequency = <400000>;
 	status = "okay";
+
+	touchscreen@48 {
+		compatible = "nsiway,ns2009";
+		reg = <0x48>;
+		touchscreen-min-pressure = <150>;
+		touchscreen-inverted-y;
+	};
 };
 
 &io_domains {

base-commit: f4f7ecd2e0e8debcbab4789717cc79d570d665e3
-- 
2.56.0


                 reply	other threads:[~2026-10-10 23:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261010232908.26968-1-founder@crepuse.com \
    --to=founder@crepuse.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@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 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®