From: Frank Li <Frank.Li@nxp.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Dong Aisheng <aisheng.dong@nxp.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
stable@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH v2 8/9] arm64: dts: imx8qm-mek: fix gpio number for reg_usdhc2_vmmc
Date: Mon, 10 Jun 2024 16:46:25 -0400 [thread overview]
Message-ID: <20240610-imx8qm-dts-usb-v2-8-788417116fb1@nxp.com> (raw)
In-Reply-To: <20240610-imx8qm-dts-usb-v2-0-788417116fb1@nxp.com>
The gpio in "reg_usdhc2_vmmc" should be 7 instead of 19.
Cc: stable@vger.kernel.org
Fixes: 307fd14d4b14 ("arm64: dts: imx: add imx8qm mek support")
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
arch/arm64/boot/dts/freescale/imx8qm-mek.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
index e3a653be7dacc..8ab75cc5b9aff 100644
--- a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
+++ b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
@@ -114,7 +114,7 @@ reg_usdhc2_vmmc: usdhc2-vmmc {
regulator-name = "SD1_SPWR";
regulator-min-microvolt = <3000000>;
regulator-max-microvolt = <3000000>;
- gpio = <&lsio_gpio4 19 GPIO_ACTIVE_HIGH>;
+ gpio = <&lsio_gpio4 7 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
--
2.34.1
next prev parent reply other threads:[~2024-06-10 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 20:46 [PATCH v2 0/9] arm64: dts: imx8qm: add subsystem lvds and mipi Frank Li
2024-06-10 20:46 ` [PATCH v2 1/9] arm64: dts: imx8: add basic lvds and lvds2 subsystem Frank Li
2024-06-11 10:05 ` Alexander Stein
2024-06-12 15:13 ` Frank Li
2024-06-10 20:46 ` [PATCH v2 2/9] arm64: dts: imx8qm: add lvds subsystem Frank Li
2024-06-10 20:46 ` [PATCH v2 3/9] arm64: dts: imx8: add basic mipi subsystem Frank Li
2024-06-11 11:14 ` Alexander Stein
2024-06-11 15:03 ` Frank Li
2024-06-10 20:46 ` [PATCH v2 4/9] arm64: dts: imx8qm: add " Frank Li
2024-06-10 20:46 ` [PATCH v2 5/9] arm64: dts: imx8qm-mek: add cm4 remote-proc and related memory region Frank Li
2024-06-10 20:46 ` [PATCH v2 6/9] arm64: dts: imx8qm-mek: add pwm and i2c in lvds subsystem Frank Li
2024-06-10 20:46 ` [PATCH v2 7/9] arm64: dts: imx8qm-mek: add i2c in mipi[0,1] subsystem Frank Li
2024-06-10 20:46 ` Frank Li [this message]
2024-06-10 20:46 ` [PATCH v2 9/9] arm64: dts: imx8qm-mek: add usb 3.0 and related type C nodes Frank Li
2024-06-10 21:08 ` [PATCH v2 0/9] arm64: dts: imx8qm: add subsystem lvds and mipi Frank Li
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=20240610-imx8qm-dts-usb-v2-8-788417116fb1@nxp.com \
--to=frank.li@nxp.com \
--cc=aisheng.dong@nxp.com \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).