From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: gene_chen@richtek.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux@roeck-us.net,
heikki.krogerus@linux.intel.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings usb: typec: rt1718s: Add binding for Richtek RT1718S
Date: Mon, 9 Jan 2023 11:14:03 +0100 [thread overview]
Message-ID: <3aa83ec3-228d-1add-5e4b-c100340b127e@linaro.org> (raw)
In-Reply-To: <1673256674-25165-1-git-send-email-gene_chen@richtek.com>
On 09/01/2023 10:31, gene_chen@richtek.com wrote:
> From: Gene Chen <gene_chen@richtek.com>
>
Subject: drop second, redundant "binding for".
> Add binding for Richtek RT1718s
>
> Signed-off-by: Gene Chen <gene_chen@richtek.com>
> ---
> .../devicetree/bindings/usb/richtek,rt1718s.yaml | 98 ++++++++++++++++++++++
> 1 file changed, 98 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/richtek,rt1718s.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/richtek,rt1718s.yaml b/Documentation/devicetree/bindings/usb/richtek,rt1718s.yaml
> new file mode 100644
> index 00000000..7797fc6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/richtek,rt1718s.yaml
> @@ -0,0 +1,98 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/usb/richtek,rt1718s.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
Drop quotes from both.
> +
> +title: Richtek RT1718S Type-C Port Switch and Power Delivery controller
> +
> +maintainers:
> + - Gene Chen <gene_chen@richtek.com>
> +
> +description: |
> + The RT1718S is a USB Type-C controller that complies with the latest
> + USB Type-C and PD standards. It does the USB Type-C detection including attach
> + and orientation. It integrates the physical layer of the USB BMC power
> + delivery protocol to allow up to 100W of power. The BMC PD block enables full
> + support for alternative interfaces of the Type-C specification.
> +
> +properties:
> + compatible:
> + enum:
> + - richtek,rt1718s
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + wakeup-source:
> + description: enable IRQ remote wakeup, see power/wakeup-source.txt
Drop description, you are copying generic description.
> + type: boolean
Drop. Just wakeup-soource: true
> +
> + connector:
> + type: object
> + $ref: ../connector/usb-connector.yaml#
Full path, so /schemas/usb/connector ....
> + description:
> + Properties for usb c connector.
That's not accurate description. Everything in properties is a property,
so no need to say that properties are properties.
Actually this looks the same as existing rt1711, so please do not
duplicate stuff. Especially, do not duplicate mistakes...
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - connector
> + - interrupts
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/usb/pd.h>
> + i2c0 {
i2c
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + rt1718s@43 {
Node names should be generic.
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
Best regards,
Krzysztof
prev parent reply other threads:[~2023-01-09 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:31 [PATCH 1/2] dt-bindings usb: typec: rt1718s: Add binding for Richtek RT1718S gene_chen
2023-01-09 9:31 ` [PATCH 2/2] usb: typec: tcpci_rt1718s: Add Richtek RT1718S tcpci driver gene_chen
2023-01-09 10:17 ` Krzysztof Kozlowski
2023-01-09 18:52 ` Guenter Roeck
[not found] ` <2af0661f930d4393bda9f7e771654bac@richtek.com>
2023-01-12 8:05 ` FW: " Gene Chen
2023-01-12 14:18 ` Guenter Roeck
2023-01-09 10:14 ` Krzysztof Kozlowski [this message]
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=3aa83ec3-228d-1add-5e4b-c100340b127e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gene_chen@richtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).