From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Allen_Lin <allencl_lin@hotmail.com>,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
jikos@kernel.org, benjamin.tissoires@redhat.com,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: input: Add Himax HX83102J touchscreen
Date: Wed, 6 Dec 2023 11:37:48 +0100 [thread overview]
Message-ID: <6e8a6fc2-88c2-4655-a8f0-45ece45170e2@linaro.org> (raw)
In-Reply-To: <TY0PR06MB56116A355D2A5BF665FA0D899E85A@TY0PR06MB5611.apcprd06.prod.outlook.com>
On 05/12/2023 11:05, Allen_Lin wrote:
> Add the HX83102j touchscreen device tree bindings documents.
>
> Signed-off-by: Allen_Lin <allencl_lin@hotmail.com>
> ---
> .../bindings/input/himax,hx8310xx.yaml | 70 +++++++++++++++++++
> MAINTAINERS | 6 ++
> 2 files changed, 76 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/himax,hx8310xx.yaml
>
> diff --git a/Documentation/devicetree/bindings/input/himax,hx8310xx.yaml b/Documentation/devicetree/bindings/input/himax,hx8310xx.yaml
> new file mode 100644
> index 000000000000..1cc65e9bd267
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/himax,hx8310xx.yaml
Filename like compatible, so himax,hx83102j.yaml
> @@ -0,0 +1,70 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/himax,hx8310xx.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: himax hx8310xx touchscreen
Himax? HiMax? lowercase "himax" seems wrong and your commit msg also
suggest different capitalization. The same for "hx8310xx". And it is not
"xx" but 2J.
> +
> +maintainers:
> + - Allen Lin <allencl_lin@hotmail.com>
> +
> +description:
> + Supports the himax hx8310xx touchscreen.
Drop sentence, instead describe hardware like "Himax HX83102J is a
touchscreen connected over SPI ...."
> + This touchscreen uses the spi-hid protocol but has some non-standard
> + power sequencing required.
> +
> +allOf:
> + - $ref: /schemas/input/touchscreen/touchscreen.yaml#
Missing ref to spi-peripheral-props
> +
> +properties:
> + compatible:
> + enum:
> + - himax,hx83102j
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + reset-gpios:
> + maxItems: 1
> +
> + spi-cpha: true
> +
> + spi-cpol: true
> +
> + spi-max-frequency: true
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - reset-gpios
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,rpmh.h>
Why? Drop
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + hid_himax_spi@0 {
No underscores in node names.
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + pinctrl-names = "default";
> + pinctrl-0 = <&touch_int0 &touch_reset>;
> + reg = <0>;
Oh damn... ok, so compatible is always the first property. Reg is second.
> + spi-max-frequency = <12500000>;
> + status = "okay";
Drop
> + compatible = "himax,hx83102j";
> + reset-gpios = <&gpio1 8 GPIO_ACTIVE_LOW>;
> + spi-cpha;
> + spi-cpol;
> + interrupt-parent = <&gpio1>;
> + interrupts = <7 IRQ_TYPE_LEVEL_LOW>;
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-06 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231205100552.723620-1-allencl_lin@hotmail.com>
2023-12-05 10:05 ` Allen_Lin
2023-12-06 10:37 ` Krzysztof Kozlowski [this message]
2023-12-05 10:05 ` [PATCH v1 2/2] Input: Add Himax HX83102J touchscreen driver Allen_Lin
2023-12-05 18:07 ` kernel test robot
2023-12-05 20:19 ` kernel test robot
2023-12-05 21:56 ` kernel test robot
2023-12-06 10:58 ` Krzysztof Kozlowski
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=6e8a6fc2-88c2-4655-a8f0-45ece45170e2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=allencl_lin@hotmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®