From: "Eric Gonçalves" <ghatto404@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Ivaylo Ivanov" <ivo.ivanov.ivanov1@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Eric Gonçalves" <ghatto404@gmail.com>
Subject: [RFC PATCH 1/2] dt-bindings: input: add ST-Microelectronics FTS2BA61Y touchscreen binding
Date: Thu, 11 Sep 2025 21:19:09 +0000 [thread overview]
Message-ID: <20250911211910.45903-2-ghatto404@gmail.com> (raw)
In-Reply-To: <20250911211910.45903-1-ghatto404@gmail.com>
Add the bindings for ST-Microelectronics FTS2BA61Y capacitive touchscreen.
Signed-off-by: Eric Gonçalves <ghatto404@gmail.com>
---
.../input/touchscreen/st,fts2ba61y.yaml | 52 +++++++++++++++++++
1 file changed, 52 insertions(+)
create mode 100755 Documentation/devicetree/bindings/input/touchscreen/st,fts2ba61y.yaml
diff --git a/Documentation/devicetree/bindings/input/touchscreen/st,fts2ba61y.yaml b/Documentation/devicetree/bindings/input/touchscreen/st,fts2ba61y.yaml
new file mode 100644
index 000000000000..e4d076bc7bcd
--- /dev/null
+++ b/Documentation/devicetree/bindings/input/touchscreen/st,fts2ba61y.yaml
@@ -0,0 +1,52 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/input/touchscreen/st,fts2ba61y.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ST-Microelectronics FTS2BA61Y touchscreen controller
+
+maintainers:
+ - Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
+
+allOf:
+ - $ref: touchscreen.yaml#
+
+properties:
+ compatible:
+ const: st,fts2ba61y
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ avdd-supply: true
+ vdd-supply: true
+
+unevaluatedProperties: false
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - avdd-supply
+ - vdd-supply
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ touchscreen@0 {
+ compatible = "st,fts2ba61y";
+ reg = <0x0>;
+ interrupt-parent = <&gpa2>;
+ interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
+ avdd-supply = <&ldo17_reg>;
+ vdd-supply = <&ldo28_reg>;
+ };
+ };
--
2.50.1
next prev parent reply other threads:[~2025-09-11 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 21:19 [RFC PATCH 0/2] Input: add fts2ba61y touchscreen driver Eric Gonçalves
2025-09-11 21:19 ` Eric Gonçalves [this message]
2025-09-14 14:48 ` [RFC PATCH 1/2] dt-bindings: input: add ST-Microelectronics FTS2BA61Y touchscreen binding Krzysztof Kozlowski
2025-09-14 16:16 ` Eric Gonçalves
2025-09-14 16:46 ` Krzysztof Kozlowski
2025-09-11 21:19 ` [RFC PATCH 2/2] Input: add support for the STM FTS2BA61Y touchscreen Eric Gonçalves
2025-09-14 14:47 ` [RFC PATCH 0/2] Input: add fts2ba61y touchscreen driver Krzysztof Kozlowski
2025-09-14 14:53 ` Ivaylo Ivanov
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=20250911211910.45903-2-ghatto404@gmail.com \
--to=ghatto404@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rydberg@bitmath.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;
as well as URLs for NNTP newsgroup(s).