From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: TY Chang <tychang@realtek.com>,
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, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio
Date: Thu, 7 Dec 2023 14:54:55 +0100 [thread overview]
Message-ID: <dd22f0fb-e07b-4bd4-bd6a-cf2d8a5687fc@linaro.org> (raw)
In-Reply-To: <20231207100723.15015-2-tychang@realtek.com>
On 07/12/2023 11:07, TY Chang wrote:
> From: Tzuyi Chang <tychang@realtek.com>
>
> Add the device tree bindings for the Realtek DHC(Digital Home Center)
> RTD SoCs GPIO controllers.
>
> Signed-off-by: Tzuyi Chang <tychang@realtek.com>
> ---
> v2 to v3 change:
> 1. Remove generic compatible and use SoC-specific compatible instead.
> v1 to v2 change:
> 1. Add description for DHC RTD SoCs.
> 2. Revise the compatible names.
> 3. Add descriptions for reg and interrupts properties.
> ---
> .../bindings/gpio/realtek,rtd-gpio.yaml | 69 +++++++++++++++++++
> 1 file changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
>
> 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..984e7dbd322e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
> @@ -0,0 +1,69 @@
> +# 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
> +
> +maintainers:
> + - Tzuyi Chang <tychang@realtek.com>
> +
> +description:
> + The GPIO controller is designed for the Realtek DHC (Digital Home Center)
> + RTD series SoC family, which are high-definition media processor SoCs.
> +
> +properties:
> + compatible:
> + enum:
> + - realtek,rtd1295-misc-gpio
> + - realtek,rtd1295-iso-gpio
> + - realtek,rtd1395-iso-gpio
> + - realtek,rtd1619-iso-gpio
> + - realtek,rtd1319-iso-gpio
> + - realtek,rtd1619b-iso-gpio
> + - realtek,rtd1319d-iso-gpio
> + - realtek,rtd1315e-iso-gpio
If there is going to be resend, please order this list alphanumerically.
> +
> + reg:
> + items:
> + - description: GPIO controller registers
> + - description: GPIO interrupt registers
> +
...
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + gpio@100 {
> + compatible = "realtek,rtd1319d-iso-gpio";
> + reg = <0x100 0x100>,
> + <0x000 0x0b0>;
That's odd. Why order is decreasing? Isn't 0x0 the address of the SoC
(soc@0)?
It is, btw, 0x0, not 0x000. The same for 0x0b0 -> 0xb0, unless you want
to pad to full word.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-07 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 10:07 [PATCH v3 0/2] Add gpio driver support for Realtek DHC SoCs TY Chang
2023-12-07 10:07 ` [PATCH v3 1/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio TY Chang
2023-12-07 13:54 ` Krzysztof Kozlowski [this message]
2023-12-08 9:03 ` TY_Chang[張子逸]
2023-12-08 12:19 ` Krzysztof Kozlowski
2023-12-07 10:07 ` [PATCH v3 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs TY Chang
2023-12-07 13:45 ` Andy Shevchenko
2023-12-12 9:55 ` TY_Chang[張子逸]
2023-12-13 13:40 ` Andy Shevchenko
2023-12-14 7:57 ` TY_Chang[張子逸]
2023-12-14 13:58 ` Andy Shevchenko
2023-12-14 14:35 ` Michael Walle
2023-12-14 14:49 ` Andy Shevchenko
2023-12-15 6:50 ` TY_Chang[張子逸]
2023-12-18 8:50 ` Michael Walle
[not found] ` <202312181420.3BIEK9gtC1692907@rtits1.realtek.com.tw>
2023-12-20 7:13 ` TY_Chang[張子逸]
2023-12-15 3:29 ` TY_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=dd22f0fb-e07b-4bd4-bd6a-cf2d8a5687fc@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tychang@realtek.com \
/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).