From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org,
Chris Morgan <macroalpha82@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 4/4] arm64: dts: rockchip: Describe Alternate Regulator Config on RGB30
Date: Thu, 11 Apr 2024 20:42:44 +0200 [thread overview]
Message-ID: <2252888.taCxCBeP46@phil> (raw)
In-Reply-To: <20240325175133.19393-5-macroalpha82@gmail.com>
Am Montag, 25. März 2024, 18:51:33 CEST schrieb Chris Morgan:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Describe a possible secondary regulator configuration for the RGB30.
> At some point Powkiddy altered the CPU regulator for the RGB30 without
> creating a new model revision. Note this in the device-tree in the
> hopes that it may alleviate a user's confusion (or possibly allow a
> bootloader to manipulate the tree to swap out the regulators when the
> alternate configuration is detected).
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
I don't think this is the correct approach here, we'll really need
a second board dts for the variant.
Only describing the regulator in a comment does not help the affected
users at all, as they would need to adapt the dt they have on their
device on each update.
Having a second dtb will have the kernel build both (also improving
build testing) and allow them to configure their bootloader to load
the correct one, even if we can't detect the variant device automatically.
Heiko
> ---
> .../dts/rockchip/rk3566-powkiddy-rgb30.dts | 24 +++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb30.dts b/arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb30.dts
> index e359465eebe9..484f097e9f11 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb30.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb30.dts
> @@ -54,6 +54,30 @@ regulator-state-mem {
> regulator-off-in-suspend;
> };
> };
> +
> + /*
> + * Some RGB30 devices use a different CPU regulator. These
> + * devices have no external markings to denote a different
> + * model revision.
> + */
> + vdd_cpu_alt: regulator@40 {
> + compatible = "tcs,tcs4525";
> + reg = <0x40>;
> + fcs,suspend-voltage-selector = <1>;
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <712500>;
> + regulator-max-microvolt = <1390000>;
> + regulator-name = "vdd_cpu_alt";
> + regulator-ramp-delay = <2300>;
> + vin-supply = <&vcc_sys>;
> +
> + status = "disabled";
> +
> + regulator-state-mem {
> + regulator-off-in-suspend;
> + };
> + };
> };
>
> &sdmmc2 {
>
next prev parent reply other threads:[~2024-04-11 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:51 [PATCH 0/4] User Requested Fixes for Powkiddy RK3566 Devices Chris Morgan
2024-03-25 17:51 ` [PATCH 1/4] dts: rockchip: Add chasis-type for Powkiddy rk3566 devices Chris Morgan
2024-03-25 17:51 ` [PATCH 2/4] arm64: dts: rockchip: Update sdmmc node for wifi on powkiddy rk3566 Chris Morgan
2024-03-25 17:51 ` [PATCH 3/4] arm64: dts: rockchip: Correct model name for Powkiddy RK3566 Devices Chris Morgan
2024-03-25 17:51 ` [PATCH 4/4] arm64: dts: rockchip: Describe Alternate Regulator Config on RGB30 Chris Morgan
2024-04-11 18:42 ` Heiko Stuebner [this message]
2024-03-25 17:57 ` [PATCH 0/4] User Requested Fixes for Powkiddy RK3566 Devices Dragan Simic
2024-03-25 21:53 ` Heiko Stübner
2024-03-25 21:58 ` Dragan Simic
2024-03-25 22:10 ` Chris Morgan
2024-04-11 18:29 ` (subset) " Heiko Stuebner
2024-04-12 14:35 ` Chris Morgan
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=2252888.taCxCBeP46@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.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