From: Samuel Holland <samuel.holland@sifive.com>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>,
Pritesh Patel <pritesh.patel@einfochips.com>,
Min Lin <linmin@eswincomputing.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
鲁玉林 <luyulin@eswincomputing.com>, 宁宇 <ningyu@eswincomputing.com>,
"Lin Feng" <fenglin@eswincomputing.com>
Subject: Re: [RFC PATCH 3/4] riscv: dts: Add EIC7700 pin controller node
Date: Tue, 25 Mar 2025 16:49:14 -0500 [thread overview]
Message-ID: <a20d5849-770e-420d-b707-83a50c37810b@sifive.com> (raw)
In-Reply-To: <20250325141311.758787-4-emil.renner.berthing@canonical.com>
On 2025-03-25 9:13 AM, Emil Renner Berthing wrote:
> Add node for the pin controller on the ESWIN EIC7700 SoC and gpio-ranges
> properties mapping GPIOs to pins.
>
> Signed-off-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
> ---
> arch/riscv/boot/dts/eswin/eic7700.dtsi | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/eswin/eic7700.dtsi b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> index 9cef940f07e4..7226647919b7 100644
> --- a/arch/riscv/boot/dts/eswin/eic7700.dtsi
> +++ b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> @@ -312,6 +312,13 @@ porta: gpio-port@0 {
> <324>, <325>, <326>, <327>, <328>, <329>, <330>,
> <331>, <332>, <333>, <334>;
> gpio-controller;
> + gpio-ranges = <&pinctrl 0 12 1>,
> + <&pinctrl 1 14 12>,
> + <&pinctrl 13 1 4>,
> + <&pinctrl 17 32 1>,
> + <&pinctrl 18 40 5>,
> + <&pinctrl 23 51 7>,
> + <&pinctrl 30 68 2>;
> ngpios = <32>;
> #gpio-cells = <2>;
> };
> @@ -320,6 +327,9 @@ portb: gpio-port@1 {
> compatible = "snps,dw-apb-gpio-port";
> reg = <1>;
> gpio-controller;
> + gpio-ranges = <&pinctrl 0 70 3>,
> + <&pinctrl 3 79 7>,
> + <&pinctrl 10 89 22>;
> ngpios = <32>;
> #gpio-cells = <2>;
> };
> @@ -328,6 +338,7 @@ portc: gpio-port@2 {
> compatible = "snps,dw-apb-gpio-port";
> reg = <2>;
> gpio-controller;
> + gpio-ranges = <&pinctrl 0 111 32>;
> ngpios = <32>;
> #gpio-cells = <2>;
> };
> @@ -336,9 +347,15 @@ portd: gpio-port@3 {
> compatible = "snps,dw-apb-gpio-port";
> reg = <3>;
> gpio-controller;
> + gpio-ranges = <&pinctrl 0 143 16>;
> ngpios = <16>;
> #gpio-cells = <2>;
> };
> };
> +
> + pinctrl: pinctrl@51600080 {
> + compatible = "eswin,eic7700-pinctrl";
> + reg = <0x0 0x51600080 0x0 0xff80>;
Per the TRM, the MMIO range is 2M-128B large, so the size should be 0x1fff80.
Other than that, the rest looks good (especially, the GPIO ranges match what I
have), so:
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
> + };
> };
> };
next prev parent reply other threads:[~2025-03-25 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 14:13 [RFC PATCH 0/4] ESWIN EIC7700 pinctrl driver Emil Renner Berthing
2025-03-25 14:13 ` [RFC PATCH 1/4] dt-bindings: pinctrl: Add eswin,eic7700-pinctrl binding Emil Renner Berthing
2025-03-25 20:49 ` Linus Walleij
2025-03-26 0:44 ` Yixun Lan
2025-03-26 8:20 ` Krzysztof Kozlowski
2025-03-26 9:57 ` Emil Renner Berthing
2025-03-29 4:42 ` Krzysztof Kozlowski
2025-03-25 14:13 ` [RFC PATCH 2/4] pinctrl: Add driver for the ESWIN EIC7700 RISC-V SoC Emil Renner Berthing
2025-03-25 21:45 ` Samuel Holland
2025-03-25 14:13 ` [RFC PATCH 3/4] riscv: dts: Add EIC7700 pin controller node Emil Renner Berthing
2025-03-25 21:49 ` Samuel Holland [this message]
2025-03-25 14:13 ` [RFC PATCH 4/4] riscv: dts: eswin: Add HiFive Premier UART pin control Emil Renner Berthing
2025-03-25 21:19 ` [RFC PATCH 0/4] ESWIN EIC7700 pinctrl driver Samuel Holland
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=a20d5849-770e-420d-b707-83a50c37810b@sifive.com \
--to=samuel.holland@sifive.com \
--cc=alex@ghiti.fr \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=fenglin@eswincomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luyulin@eswincomputing.com \
--cc=ningyu@eswincomputing.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=pritesh.patel@einfochips.com \
--cc=robh@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®