From: "Dragan Simic" <dsimic@manjaro.org>
To: "Diederik de Haas" <diederik@cknow-tech.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
"Johan Jonker" <jbx6244@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Fix vccio4-supply on rk3566-pinetab2
Date: Sun, 26 Oct 2025 18:36:15 +0100 [thread overview]
Message-ID: <e2caefd1-9668-0404-598f-98b26375525c@manjaro.org> (raw)
In-Reply-To: <20251026172608.108956-1-diederik@cknow-tech.com>
Hello Diederik,
On Sunday, October 26, 2025 18:25 CET, Diederik de Haas <diederik@cknow-tech.com> wrote:
> Page 13 of the PineTab2 v2 schematic dd 20230417 shows VCCIO4's power
> source is VCCIO_WL. Page 19 shows that VCCIO_WL is connected to
> VCCA1V8_PMU, so fix the PineTab2 dtsi to reflect that.
>
> Signed-off-by: Diederik de Haas <diederik@cknow-tech.com>
Thanks for this patch. As already discussed in private, this is
correct and safe to do, because both supplies are designated as
always-on, so please feel free to include:
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
Though, I think this cleanup should also be propagated into the
stable kernels. Right now this patch doesn't actually introduce
any functional changes, but maybe in the future there will be
some related driver or DT changes or improvements that may end up
relying on DT correction such as this one.
> ---
> arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi
> index d0e38412d56a..08bf40de17ea 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi
> @@ -789,7 +789,7 @@ &pmu_io_domains {
> vccio1-supply = <&vccio_acodec>;
> vccio2-supply = <&vcc_1v8>;
> vccio3-supply = <&vccio_sd>;
> - vccio4-supply = <&vcc_1v8>;
> + vccio4-supply = <&vcca1v8_pmu>;
> vccio5-supply = <&vcc_1v8>;
> vccio6-supply = <&vcc1v8_dvp>;
> vccio7-supply = <&vcc_3v3>;
next prev parent reply other threads:[~2025-10-26 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 17:25 Diederik de Haas
2025-10-26 17:36 ` Dragan Simic [this message]
2025-10-26 18:44 ` Diederik de Haas
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=e2caefd1-9668-0404-598f-98b26375525c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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®