From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH v1 2/2] dt-bindings: extcon: Add Realtek DHC RTD SoC Type-C
Date: Thu, 24 Aug 2023 06:03:02 +0000 [thread overview]
Message-ID: <ca406c19e59145fd9e7e035ea5ad3eeb@realtek.com> (raw)
In-Reply-To: <1e0632d6-73e9-4633-a709-bf9140f2fd32@linaro.org>
Hi Krzysztof,
> On 22/08/2023 12:28, Stanley Chang wrote:
> > Document the device-tree bindings for Realtek SoCs Type-C.
> > Realtek DHC (digital home center) RTD SoCs support a Type-C module.
> >
> > Signed-off-by: Stanley Chang <stanley_chang@realtek.com>
> > ---
> > .../bindings/extcon/extcon-rtk-type-c.yaml | 77 +++++++++++++++++++
> > 1 file changed, 77 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/extcon/extcon-rtk-type-c.yaml
>
> Filename like compatible.
I will rename.
> >
> > diff --git
> > a/Documentation/devicetree/bindings/extcon/extcon-rtk-type-c.yaml
> > b/Documentation/devicetree/bindings/extcon/extcon-rtk-type-c.yaml
> > new file mode 100644
> > index 000000000000..d14b9ee544b9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/extcon/extcon-rtk-type-c.yaml
> > @@ -0,0 +1,77 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) # Copyright
> > +2023 Realtek Semiconductor Corporation %YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/extcon/extcon-rtk-type-c.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Realtek DHC RTD SoCs USB Type-C detection
>
> Type-c usually go to usb directory.
This binding is not for a type-c controller.
It is an extcon device for type-c connector detection.
So I put it at extcon directory.
And I will add “connector” to the title.
title: Realtek DHC RTD SoCs USB Type-C Connector detection
> > +maintainers:
> > + - Stanley Chang <stanley_chang@realtek.com>
> > +
> > +description: |
>
> Do not need '|' unless you need to preserve formatting.
Ok
> > + Realtek digital home center (DHC) RTD series SoCs include a type c
> module.
> > + This module is able to detect the state of type c connector.
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - realtek,rtd1295-type-c
> > + - realtek,rtd1312c-type-c
> > + - realtek,rtd1315e-type-c
> > + - realtek,rtd1319-type-c
> > + - realtek,rtd1319d-type-c
> > + - realtek,rtd1395-type-c
> > + - realtek,rtd1619-type-c
> > + - realtek,rtd1619b-type-c
> > +
> > + reg:
> > + maxItems: 1
> > + description: Address and length of register set for type-c module.
>
> Drop description, it's obvious.
Ok.
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + nvmem-cells:
> > + maxItems: 1
> > + description:
> > + The phandle to nvmem cell that contains the trimming data.
> > + If unspecified, default value is used.
> > +
> > + pinctrl-names:
> > + const: default
> > + description: A pinctrl state names "default" must be defined.
>
> Drop, property not needed.
Ok
> > +
> > + pinctrl-0:
> > + description:
> > + Should contain default pinctrl.
>
> Drop, property not needed.
>
Ok.
>
> > +
> > + nvmem-cell-names:
> > + const: usb-cal
>
> items:
> - const: usb-cal
>
> and move description to nvmem-cells.
>
> > + description:
> > + The type c parameter trimming data specified via efuse.
>
> Keep same properties next to each other. nvmem-cells should be followed by
> nvmem-cell-names.
>
> > +
> > + realtek,rd-ctrl-gpio:
> > + description: The gpio node to control external Rd on board.
>
> The names are always "gpios".
Do you mean "realtek,rd-ctrl-gpios" ?
>
> > + maxItems: 1
> > +
>
> You miss here connector. Probably also VBUS supply and other supplies.
>
Ok, I will add connector.
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + type-c@7220 {
> > + compatible = "realtek,rtd1619b-type-c";
> > + reg = <0x7220 0x20>;
> > + interrupts = <0 60 4>;
>
> Use proper defines for common constants.
Ok, I will revise this.
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&usb_cc1_pins>, <&usb_cc2_pins>;
You mention that the property of pinctrl not need in doc.
Do I need to add the property of pintrl in example?
> > + nvmem-cells = <&otp_usb_cal>;
> > + nvmem-cell-names = "usb-cal";
>
> Type-c without connector? This is incomplete.
Ok, I will add connector.
Thanks,
Stanley
next prev parent reply other threads:[~2023-08-24 6:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:28 [PATCH v1 1/2] extcon: add Realtek DHC RTD SoC Type-C driver Stanley Chang
2023-08-22 10:28 ` [PATCH v1 2/2] dt-bindings: extcon: Add Realtek DHC RTD SoC Type-C Stanley Chang
2023-08-22 15:38 ` Krzysztof Kozlowski
2023-08-24 6:03 ` Stanley Chang[昌育德] [this message]
2023-08-24 6:26 ` Krzysztof Kozlowski
2023-08-24 7:23 ` Stanley Chang[昌育德]
2023-08-24 8:43 ` Krzysztof Kozlowski
2023-08-24 9:23 ` Stanley Chang[昌育德]
2023-08-24 9:56 ` Krzysztof Kozlowski
2023-08-24 10:05 ` Stanley Chang[昌育德]
2023-08-22 15:35 ` [PATCH v1 1/2] extcon: add Realtek DHC RTD SoC Type-C driver Krzysztof Kozlowski
2023-08-24 6:09 ` Stanley Chang[昌育德]
2023-08-23 0:26 ` kernel test robot
2023-08-23 14:15 ` kernel test robot
2023-08-24 19:43 ` Chanwoo Choi
2023-08-25 9:39 ` Stanley Chang[昌育德]
2023-08-29 11:15 ` Stanley Chang[昌育德]
2023-08-29 19:18 ` Chanwoo Choi
2023-08-30 3:59 ` Stanley Chang[昌育德]
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=ca406c19e59145fd9e7e035ea5ad3eeb@realtek.com \
--to=stanley_chang@realtek.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.