From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stefan Agner <stefan@agner.ch>,
Dong Aisheng <aisheng.dong@nxp.com>,
Jacky Bai <ping.bai@nxp.com>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH v3 09/11] arm64: dts: imx95: fix gpio clocks
Date: Thu, 05 Nov 2026 11:53:07 +0800 [thread overview]
Message-ID: <20261105-gpio-vf610-fixes-v3-9-504e19de5ad5@nxp.com> (raw)
In-Reply-To: <20261105-gpio-vf610-fixes-v3-0-504e19de5ad5@nxp.com>
From: Peng Fan <peng.fan@nxp.com>
Per reference mannual [1], 69.3.5 Clocking:
GPIO receives a single clock, which is used for register access and
synchronization with external pin inputs. So drop the 'port' clock.
[1] https://www.nxp.com/docs/en/reference-manual/IMX95RM.pdf
Fixes: 5e3cbb8e4256 ("arm64: dts: freescale: add i.MX95 basic dtsi")
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
arch/arm64/boot/dts/freescale/imx95.dtsi | 25 ++++++++++---------------
1 file changed, 10 insertions(+), 15 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
index d20c2498b9aa..0398de491553 100644
--- a/arch/arm64/boot/dts/freescale/imx95.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
@@ -1300,9 +1300,8 @@ gpio2: gpio@43810000 {
<GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller;
#interrupt-cells = <2>;
- clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>,
- <&scmi_clk IMX95_CLK_BUSWAKEUP>;
- clock-names = "gpio", "port";
+ clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>;
+ clock-names = "gpio";
gpio-ranges = <&scmi_iomuxc 0 4 32>;
ngpios = <32>;
};
@@ -1316,9 +1315,8 @@ gpio3: gpio@43820000 {
<GIC_SPI 52 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller;
#interrupt-cells = <2>;
- clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>,
- <&scmi_clk IMX95_CLK_BUSWAKEUP>;
- clock-names = "gpio", "port";
+ clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>;
+ clock-names = "gpio";
gpio-ranges = <&scmi_iomuxc 0 104 8>, <&scmi_iomuxc 8 74 18>,
<&scmi_iomuxc 26 42 2>, <&scmi_iomuxc 28 0 4>;
ngpios = <32>;
@@ -1333,9 +1331,8 @@ gpio4: gpio@43840000 {
<GIC_SPI 54 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller;
#interrupt-cells = <2>;
- clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>,
- <&scmi_clk IMX95_CLK_BUSWAKEUP>;
- clock-names = "gpio", "port";
+ clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>;
+ clock-names = "gpio";
gpio-ranges = <&scmi_iomuxc 0 46 28>, <&scmi_iomuxc 28 44 2>;
ngpios = <30>;
};
@@ -1349,9 +1346,8 @@ gpio5: gpio@43850000 {
<GIC_SPI 56 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller;
#interrupt-cells = <2>;
- clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>,
- <&scmi_clk IMX95_CLK_BUSWAKEUP>;
- clock-names = "gpio", "port";
+ clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>;
+ clock-names = "gpio";
gpio-ranges = <&scmi_iomuxc 0 92 12>, <&scmi_iomuxc 12 36 6>;
ngpios = <18>;
};
@@ -1689,9 +1685,8 @@ gpio1: gpio@47400000 {
<GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller;
#interrupt-cells = <2>;
- clocks = <&scmi_clk IMX95_CLK_M33>,
- <&scmi_clk IMX95_CLK_M33>;
- clock-names = "gpio", "port";
+ clocks = <&scmi_clk IMX95_CLK_M33>;
+ clock-names = "gpio";
gpio-ranges = <&scmi_iomuxc 0 112 16>;
ngpios = <16>;
status = "disabled";
--
2.51.0
next prev parent reply other threads:[~2026-11-05 3:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 3:52 [PATCH v3 00/11] gpio: vf610: fix clocks and misc cleanup Peng Fan (OSS)
2026-11-05 3:52 ` [PATCH v3 01/11] dt-bindings: gpio: vf610: fix clock requirements per SoC Peng Fan (OSS)
2026-11-05 12:30 ` Peng Fan
2026-11-05 17:22 ` Frank Li
2026-11-05 3:53 ` [PATCH v3 02/11] gpio: vf610: simplify with irq_set_irq_wake() Peng Fan (OSS)
2026-11-05 17:23 ` Frank Li
2026-11-05 3:53 ` [PATCH v3 03/11] gpio: vf610: use devm_clk_get_optional_enabled() for clock handling Peng Fan (OSS)
2026-11-05 17:25 ` Frank Li
2026-11-05 3:53 ` [PATCH v3 04/11] gpio: vf610: drop unneeded header Peng Fan (OSS)
2026-11-05 3:53 ` [PATCH v3 05/11] gpio: vf610: drop unnecessary wrappers Peng Fan (OSS)
2026-11-05 3:53 ` [PATCH v3 06/11] MAINTAINERS: Add VF610 GPIO driver support Peng Fan (OSS)
2026-11-05 3:53 ` [PATCH v3 07/11] arm64: dts: imx8ulp: fix gpio clocks Peng Fan (OSS)
2026-11-05 3:53 ` [PATCH v3 08/11] arm64: dts: imx93: " Peng Fan (OSS)
2026-11-05 3:53 ` Peng Fan (OSS) [this message]
2026-11-05 3:53 ` [PATCH v3 10/11] arm64: dts: imx952: " Peng Fan (OSS)
2026-11-05 3:53 ` [PATCH v3 11/11] arm64: dts: imx94: add clocks for gpio controller Peng Fan (OSS)
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=20261105-gpio-vf610-fixes-v3-9-504e19de5ad5@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=brgl@bgdev.pl \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®