From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: linus.walleij@linaro.org, brgl@bgdev.pl, robh+dt@kernel.org,
Hector Palacios <hector.palacios@digi.com>
Cc: stefan@agner.ch, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, peng.fan@nxp.com, haibo.chen@nxp.com,
hector.palacios@digi.com
Subject: Re: [PATCH v2 2/2] arm64: dts: imx93: specify available 'ngpios' per GPIO port
Date: Mon, 15 Jan 2024 14:30:45 +0100 [thread overview]
Message-ID: <2919725.e9J7NaK4W3@steina-w> (raw)
In-Reply-To: <20240115131605.395691-3-hector.palacios@digi.com>
Hi Hector,
thanks for the patch.
Am Montag, 15. Januar 2024, 14:16:05 CET schrieb Hector Palacios:
> According to NXP HRM for i.MX93, the following GPIO pins are available:
> - GPIO1: 16 pins (0..15)
Mh, RM Rev4 (12/2023) says:
> Bit[31:17] should be Reserved for GPIO1
So GPIO1 has the range 0..16
> - GPIO2: 30 pins (0..29)
> - GPIO3: 32 pins (0..31)
> - GPIO4: 30 pins (0..29)
RM Rev4 (12/2023) says:
> Bit[31:28] should be Reserved for GPIO4
So GPIO4 would be the range 0..27
Where did you get your numbers from?
Best regards,
Alexander
>
> Signed-off-by: Hector Palacios <hector.palacios@digi.com>
> ---
> arch/arm64/boot/dts/freescale/imx93.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx93.dtsi
> b/arch/arm64/boot/dts/freescale/imx93.dtsi index 34c0540276d1..7eb2cab7c749
> 100644
> --- a/arch/arm64/boot/dts/freescale/imx93.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx93.dtsi
> @@ -970,6 +970,7 @@ gpio2: gpio@43810000 {
> <&clk IMX93_CLK_GPIO2_GATE>;
> clock-names = "gpio", "port";
> gpio-ranges = <&iomuxc 0 4 30>;
> + ngpios = <30>;
> };
>
> gpio3: gpio@43820000 {
> @@ -986,6 +987,7 @@ gpio3: gpio@43820000 {
> clock-names = "gpio", "port";
> gpio-ranges = <&iomuxc 0 84 8>, <&iomuxc 8 66
18>,
> <&iomuxc 26 34 2>, <&iomuxc 28 0
4>;
> + ngpios = <32>;
> };
>
> gpio4: gpio@43830000 {
> @@ -1001,6 +1003,7 @@ gpio4: gpio@43830000 {
> <&clk IMX93_CLK_GPIO4_GATE>;
> clock-names = "gpio", "port";
> gpio-ranges = <&iomuxc 0 38 28>, <&iomuxc 28 36
2>;
> + ngpios = <30>;
> };
>
> gpio1: gpio@47400000 {
> @@ -1016,6 +1019,7 @@ gpio1: gpio@47400000 {
> <&clk IMX93_CLK_GPIO1_GATE>;
> clock-names = "gpio", "port";
> gpio-ranges = <&iomuxc 0 92 16>;
> + ngpios = <16>;
> };
>
> ocotp: efuse@47510000 {
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2024-01-15 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:16 [PATCH v2] support i.MX93 truly available GPIO pins Hector Palacios
2024-01-15 13:16 ` [PATCH v2 1/2] gpio: vf610: add support to DT 'ngpios' property Hector Palacios
2024-01-15 21:10 ` Krzysztof Kozlowski
2024-01-15 13:16 ` [PATCH v2 2/2] arm64: dts: imx93: specify available 'ngpios' per GPIO port Hector Palacios
2024-01-15 13:30 ` Alexander Stein [this message]
2024-01-15 15:41 ` Hector Palacios
2024-01-16 2:59 ` Bough Chen
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=2919725.e9J7NaK4W3@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=hector.palacios@digi.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=stefan@agner.ch \
/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