From: Maud Spierings via B4 Relay <devnull+maud_spierings.hotmail.com@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Maud Spierings <maud_spierings@hotmail.com>
Subject: [PATCH 2/2] arm64: dts: imx93-11x11-frdm: add missing vcc-supply
Date: Sun, 06 Sep 2026 15:58:22 +0200 [thread overview]
Message-ID: <20260906-imx93_frdm_rtc-v1-2-3fadbda0bea1@hotmail.com> (raw)
In-Reply-To: <20260906-imx93_frdm_rtc-v1-0-3fadbda0bea1@hotmail.com>
From: Maud Spierings <maud_spierings@hotmail.com>
Add the power supply to the pcal6408 gpio expander, it doesn't have the
dependency loop like the pcal6524.
Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
---
arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts
index 8034992a73c7..23d2b9930420 100644
--- a/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts
+++ b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts
@@ -45,6 +45,7 @@ pcal6408: gpio@20 {
#gpio-cells = <2>;
gpio-controller;
reset-gpios = <&pcal6524 20 GPIO_ACTIVE_LOW>;
+ vcc-supply = <&buck5>;
};
};
--
2.55.0
next prev parent reply other threads:[~2026-09-06 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 13:58 [PATCH 0/2] arm64: dts: imx93-11x11-frdm: some fixes Maud Spierings via B4 Relay
2026-09-06 13:58 ` [PATCH 1/2] arm64: dts: imx93-11x11-frdm-common: fix the rtc aliases Maud Spierings via B4 Relay
2026-09-06 13:58 ` Maud Spierings via B4 Relay [this message]
2026-09-11 18:43 ` [PATCH 0/2] arm64: dts: imx93-11x11-frdm: some fixes 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=20260906-imx93_frdm_rtc-v1-2-3fadbda0bea1@hotmail.com \
--to=devnull+maud_spierings.hotmail.com@kernel.org \
--cc=Frank.Li@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=maud_spierings@hotmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).