From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joe Hung <joe_hung@ilitek.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-input@vger.kernel.org, luca_hsu@ilitek.com
Subject: Re: [PATCH v3 1/2] dt-bindings: input: touchscreen: ilitek_ts_i2c: Add bindings
Date: Sat, 20 Feb 2021 21:03:29 -0800 [thread overview]
Message-ID: <YDHpoReQXjOvEXoH@google.com> (raw)
In-Reply-To: <20210218064435.1360483-1-joe_hung@ilitek.com>
Hi Joe,
On Thu, Feb 18, 2021 at 02:44:34PM +0800, Joe Hung wrote:
> Add binding documentation for ILITEK touch devices.
>
> Signed-off-by: Joe Hung <joe_hung@ilitek.com>
> ---
> Changes in v3:
> - Add include header in examples, and pass the dt binding check
>
> Changes in v2:
> - Convert to DT schema format
> - Using interrupts instead of irq-gpios
>
> .../input/touchscreen/ilitek_ts_i2c.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ilitek_ts_i2c.yaml
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/ilitek_ts_i2c.yaml b/Documentation/devicetree/bindings/input/touchscreen/ilitek_ts_i2c.yaml
> new file mode 100644
> index 000000000000..5da9020ed272
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/touchscreen/ilitek_ts_i2c.yaml
> @@ -0,0 +1,46 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/touchscreen/ilitek_ts_i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Ilitek I2C Touchscreen Controller
> +
> +maintainers:
> + - Dmitry Torokhov <dmitry.torokhov@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - ilitek,ili2520
> + - ilitek,ili2510
> + reg:
> + const: 0x41
> + interrupts:
> + maxItems: 1
> + reset-gpios:
> + maxItems: 1
> +
> +additionalProperties: false
I think you need to make sure that wakeup-source and various
touchscreen-* properties can be used in this binding.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - reset-gpios
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/gpio/gpio.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + touchscreen@41 {
> + compatible = "ilitek,ili2520";
> + reg = <0x41>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
> + reset-gpios = <&gpio1 8 GPIO_ACTIVE_HIGH>;
> + };
> + };
> --
> 2.25.1
>
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-02-21 5:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 6:44 [PATCH v3 1/2] dt-bindings: input: touchscreen: ilitek_ts_i2c: Add bindings Joe Hung
2021-02-18 6:44 ` [PATCH v3 2/2] input: touchscreen: Add support for ILITEK Lego Series Joe Hung
2021-02-21 5:51 ` Dmitry Torokhov
2021-02-23 12:18 ` Joe Hung (洪銘陽)
2021-02-25 6:23 ` Dmitry Torokhov
2021-02-26 8:30 ` Joe Hung (洪銘陽)
2021-03-01 5:25 ` Dmitry Torokhov
2021-03-02 2:06 ` Joe Hung (洪銘陽)
2021-02-21 5:03 ` Dmitry Torokhov [this message]
2021-02-23 7:04 ` [PATCH v3 1/2] dt-bindings: input: touchscreen: ilitek_ts_i2c: Add bindings Joe Hung (洪銘陽)
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=YDHpoReQXjOvEXoH@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=luca_hsu@ilitek.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).