From: "Heiko Stübner" <heiko@sntech.de>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Jacobe Zang <jacobe.zang@wesion.com>
Cc: nick@khadas.com, efectn@protonmail.com, jagan@edgeble.ai,
dsimic@manjaro.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Jacobe Zang <jacobe.zang@wesion.com>
Subject: Re: [PATCH v2 5/5] arm64: dts: rockchip: Add cpufreq support to Khadas Edge2
Date: Mon, 17 Jun 2024 10:33:07 +0200 [thread overview]
Message-ID: <5475817.tWeucmBOSa@diego> (raw)
In-Reply-To: <20240617071112.3133101-6-jacobe.zang@wesion.com>
Hi Jacobe Zang,
Am Montag, 17. Juni 2024, 09:11:12 CEST schrieb Jacobe Zang:
> This adjust CPU nodes on Khadas Edge2.
>
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
> .../arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts b/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> index 7d7cc3e76838c..5fb15d3dc23e9 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> @@ -160,34 +160,42 @@ vdd_3v3_sd: vdd-3v3-sd-regulator {
>
> &cpu_b0 {
> cpu-supply = <&vdd_cpu_big0_s0>;
> + mem-supply = <&vdd_cpu_big0_mem_s0>;
as far as I remember there has not been any binding merged that declares
this supply. Thankfully following the double phandle below, the Edge2 is
designed to use the same regulator for the mem-supply, so special handling
isn't even needed.
Heiko
> };
>
> &cpu_b1 {
> cpu-supply = <&vdd_cpu_big0_s0>;
> + mem-supply = <&vdd_cpu_big0_mem_s0>;
> };
>
> &cpu_b2 {
> cpu-supply = <&vdd_cpu_big1_s0>;
> + mem-supply = <&vdd_cpu_big1_mem_s0>;
> };
>
> &cpu_b3 {
> cpu-supply = <&vdd_cpu_big1_s0>;
> + mem-supply = <&vdd_cpu_big1_mem_s0>;
> };
>
> &cpu_l0 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> + mem-supply = <&vdd_cpu_lit_mem_s0>;
> };
>
> &cpu_l1 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> + mem-supply = <&vdd_cpu_lit_mem_s0>;
> };
>
> &cpu_l2 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> + mem-supply = <&vdd_cpu_lit_mem_s0>;
> };
>
> &cpu_l3 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> + mem-supply = <&vdd_cpu_lit_mem_s0>;
> };
>
> &combphy0_ps {
> @@ -208,7 +216,7 @@ &i2c0 {
> pinctrl-0 = <&i2c0m2_xfer>;
> status = "okay";
>
> - vdd_cpu_big0_s0: regulator@42 {
> + vdd_cpu_big0_s0: vdd_cpu_big0_mem_s0: regulator@42 {
> compatible = "rockchip,rk8602";
> reg = <0x42>;
> fcs,suspend-voltage-selector = <1>;
> @@ -225,7 +233,7 @@ regulator-state-mem {
> };
> };
>
> - vdd_cpu_big1_s0: regulator@43 {
> + vdd_cpu_big1_s0: vdd_cpu_big1_mem_s0: regulator@43 {
> compatible = "rockchip,rk8603", "rockchip,rk8602";
> reg = <0x43>;
> fcs,suspend-voltage-selector = <1>;
>
next prev parent reply other threads:[~2024-06-17 8:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 7:11 [PATCH v2 0/5] arm64: dts: Add board support for Khadas Edge2 Jacobe Zang
2024-06-17 7:11 ` [PATCH v2 1/5] arm64: dts: rockchip: Add USB-C to Khadas Edge 2 Jacobe Zang
2024-06-17 7:11 ` [PATCH v2 2/5] arm64: dts: rockchip: Add bluetooth rfkill to Khadas Edge2 Jacobe Zang
2024-06-17 9:19 ` Alexey Charkov
2024-06-17 9:55 ` Jacobe Zang
2024-06-17 10:20 ` Alexey Charkov
2024-06-17 11:22 ` Jacobe Zang
2024-06-18 0:13 ` Sebastian Reichel
2024-06-18 2:34 ` Jacobe Zang
2024-06-17 7:11 ` [PATCH v2 3/5] arm64: dts: rockchip: Add HDMI & VOP2 to Khadas Edge 2 Jacobe Zang
2024-06-17 20:27 ` Heiko Stübner
2024-06-18 2:46 ` Jacobe Zang
2024-06-17 7:11 ` [PATCH v2 4/5] arm64: dts: rockchip: Add AP6275P wireless support " Jacobe Zang
2024-06-17 9:44 ` Alexey Charkov
2024-06-17 10:57 ` Jacobe Zang
2024-06-17 11:17 ` Alexey Charkov
2024-06-18 0:10 ` Sebastian Reichel
2024-06-18 3:27 ` Jacobe Zang
2024-06-17 7:11 ` [PATCH v2 5/5] arm64: dts: rockchip: Add cpufreq support to Khadas Edge2 Jacobe Zang
2024-06-17 8:33 ` Heiko Stübner [this message]
2024-06-17 9:09 ` Alexey Charkov
2024-06-17 9:41 ` Jacobe Zang
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=5475817.tWeucmBOSa@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=efectn@protonmail.com \
--cc=jacobe.zang@wesion.com \
--cc=jagan@edgeble.ai \
--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=nick@khadas.com \
--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;
as well as URLs for NNTP newsgroup(s).