public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "TY_Chang[張子逸]" <tychang@realtek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	"Andy Shevchenko" <andy@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio bindings
Date: Thu, 2 Nov 2023 03:11:29 +0000	[thread overview]
Message-ID: <eeded63e9e754e0e9a5b546e616be437@realtek.com> (raw)
In-Reply-To: <6a09f16e-0a41-4619-b7bb-b5561f7e36ce@linaro.org>

Hi Krzysztof,

Thank you for the review.

>On 01/11/2023 03:58, Tzuyi Chang wrote:
>> This patch adds the device tree bindings for the Realtek DHC RTD SoCs
>> GPIO controllers.
>>
>
>A nit, subject: drop second/last, redundant "bindings". The "dt-bindings" prefix is
>already stating that these are bindings.
>
I will remove it.

>> Signed-off-by: Tzuyi Chang <tychang@realtek.com>
>> ---
>>  .../bindings/gpio/realtek,rtd-gpio.yaml       | 56 +++++++++++++++++++
>>  1 file changed, 56 insertions(+)
>>  create mode 100644
>> Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
>
>How does your binding come after the user?
>

I wil move the binding to the first patch.

>>
>> diff --git
>> a/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
>> b/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
>> new file mode 100644
>> index 000000000000..6cab7ec50c88
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
>> @@ -0,0 +1,56 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) # Copyright 2023
>> +Realtek Semiconductor Corporation %YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/gpio/realtek,rtd-gpio.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Realtek DHC GPIO controller
>
>What is DHC? Where is it explained in the binding?
>

This is the abbreviation of "Digital Home Center". I will add the description to explain it.

>> +
>> +maintainers:
>> +  - TY Chang <tychang@realtek.com>
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - realtek,rtd-gpio
>
>What is "rtd"? Generic name? Drop. You cannot have generic compatibles.
>

This is a generic name for the others SoCs without the specific compatible.
I will fix it.

>
>> +      - realtek,rtd1295-misc-gpio
>> +      - realtek,rtd1295-iso-gpio
>> +      - realtek,rtd1395-iso-gpio
>> +      - realtek,rtd1619-iso-gpio
>> +
>> +  reg:
>> +    maxItems: 2
>
>You need to describe the items instead.
>

I will add the description.

>> +
>> +  interrupts:
>> +    maxItems: 2
>
>You need to describe the items instead.
>

I will add the description.

>> +
>> +  gpio-ranges: true
>> +
>> +  gpio-controller: true
>> +
>> +  "#gpio-cells":
>> +    const: 2
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - interrupts
>> +  - gpio-ranges
>> +  - gpio-controller
>> +  - "#gpio-cells"
>
>Best regards,
>Krzysztof


Thanks,
Tzuyi Chang

      reply	other threads:[~2023-11-02  3:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  2:58 [PATCH 0/2] Add gpio driver support for Realtek DHC SoCs Tzuyi Chang
2023-11-01  2:58 ` [PATCH 1/2] gpio: realtek: Add GPIO support for RTD SoC variants Tzuyi Chang
2023-11-01  7:15   ` Krzysztof Kozlowski
2023-11-02  3:30     ` TY_Chang[張子逸]
2023-11-02  7:11       ` Krzysztof Kozlowski
2023-11-03  9:09         ` TY_Chang[張子逸]
2023-11-01  8:39   ` Linus Walleij
2023-11-02 12:40     ` TY_Chang[張子逸]
2023-11-02 14:52       ` Linus Walleij
2023-11-01  2:58 ` [PATCH 2/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio bindings Tzuyi Chang
2023-11-01  7:13   ` Krzysztof Kozlowski
2023-11-02  3:11     ` TY_Chang[張子逸] [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=eeded63e9e754e0e9a5b546e616be437@realtek.com \
    --to=tychang@realtek.com \
    --cc=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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