From: Conor Dooley <conor@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK,
TOUCHSCREEN)..." <linux-input@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: touchscreen: move ar1021.txt to maxim,max11801.yaml
Date: Thu, 25 Sep 2025 20:20:02 +0100 [thread overview]
Message-ID: <20250925-boundless-announcer-007f08404112@spud> (raw)
In-Reply-To: <20250925185653.298246-1-Frank.Li@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]
On Thu, Sep 25, 2025 at 02:56:47PM -0400, Frank Li wrote:
> ar1021 have only reg and interrupts property beside touch common
> properties. So move context of ar1021.txt into maxim,max11801.yaml.
Are these devices even remotely related, other than both being touch
devices?
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> .../bindings/input/touchscreen/ar1021.txt | 15 ---------------
> .../input/touchscreen/maxim,max11801.yaml | 4 +++-
> 2 files changed, 3 insertions(+), 16 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/input/touchscreen/ar1021.txt
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/ar1021.txt b/Documentation/devicetree/bindings/input/touchscreen/ar1021.txt
> deleted file mode 100644
> index 82019bd6094ee..0000000000000
> --- a/Documentation/devicetree/bindings/input/touchscreen/ar1021.txt
> +++ /dev/null
> @@ -1,15 +0,0 @@
> -* Microchip AR1020 and AR1021 touchscreen interface (I2C)
> -
> -Required properties:
> -- compatible : "microchip,ar1021-i2c"
> -- reg : I2C slave address
> -- interrupts : touch controller interrupt
> -
> -Example:
> -
> - touchscreen@4d {
> - compatible = "microchip,ar1021-i2c";
> - reg = <0x4d>;
> - interrupt-parent = <&gpio3>;
> - interrupts = <11 IRQ_TYPE_LEVEL_HIGH>;
> - };
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/maxim,max11801.yaml b/Documentation/devicetree/bindings/input/touchscreen/maxim,max11801.yaml
> index 4f528d2201992..288c7e6e1b3b7 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/maxim,max11801.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/maxim,max11801.yaml
> @@ -11,7 +11,9 @@ maintainers:
>
> properties:
> compatible:
> - const: maxim,max11801
> + enum:
> + - maxim,max11801
> + - microchip,ar1021-i2c
>
> reg:
> maxItems: 1
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-25 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 18:56 [PATCH 1/1] dt-bindings: touchscreen: move ar1021.txt to maxim,max11801.yaml Frank Li
2025-09-25 19:20 ` Conor Dooley [this message]
2025-09-25 19:28 ` Frank Li
2025-09-25 19:46 ` Conor Dooley
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=20250925-boundless-announcer-007f08404112@spud \
--to=conor@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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