From: Hefei <3066883572@qq.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/6] dt-bindings: input: add Jadard JD9365TX touchscreen binding
Date: Thu, 19 Nov 2026 10:48:03 +0800 [thread overview]
Message-ID: <tencent_BF0B9E6C7E95501FC63D3F98AD08BEF70909@qq.com> (raw)
Add the binding for the Jadard JD9365TX in-cell touchscreen used on
the VIEWE 7KF82 module.
Signed-off-by: Hefei <3066883572@qq.com>
---
.../input/touchscreen/jadard,jd9365tx.yaml | 53 +++++++++++++++++++
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/jadard,jd9365tx.yaml
diff --git a/Documentation/devicetree/bindings/input/touchscreen/jadard,jd9365tx.yaml b/Documentation/devicetree/bindings/input/touchscreen/jadard,jd9365tx.yaml
new file mode 100644
index 0000000..23696a4
--- /dev/null
+++ b/Documentation/devicetree/bindings/input/touchscreen/jadard,jd9365tx.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/input/touchscreen/jadard,jd9365tx.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Jadard JD9365TX in-cell touchscreen
+
+maintainers:
+ - Hefei <3066883572@qq.com>
+
+description: |
+ In-cell touch integrated with Jadard JD9365TX DSI panels. The module FPC
+ often exposes only I2C (no interrupt GPIO); the driver polls coordinate
+ reports.
+
+allOf:
+ - $ref: touchscreen.yaml#
+
+properties:
+ compatible:
+ const: jadard,jd9365tx
+
+ reg:
+ maxItems: 1
+
+ poll-interval: true
+
+ jadard,coord-addr:
+ description: Optional fixed coordinate SRAM address override
+ $ref: /schemas/types.yaml#/definitions/uint32
+
+required:
+ - compatible
+ - reg
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ touchscreen@68 {
+ compatible = "jadard,jd9365tx";
+ reg = <0x68>;
+ touchscreen-size-x = <720>;
+ touchscreen-size-y = <1280>;
+ poll-interval = <16>;
+ };
+ };
+...
--
2.55.0.windows.5
reply other threads:[~2026-11-19 2:48 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=tencent_BF0B9E6C7E95501FC63D3F98AD08BEF70909@qq.com \
--to=3066883572@qq.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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®