From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [PATCH] rockchip: rk3399-puma: Restore correct VDD_LOG supply.
Date: Fri, 19 Feb 2021 11:14:28 +0100 [thread overview]
Message-ID: <4319939.GKX7oQKdZx@diego> (raw)
In-Reply-To: <20210219002948.318398-1-christoph.muellner@theobroma-systems.com>
Am Freitag, 19. Februar 2021, 01:29:48 CET schrieb Christoph Muellner:
> A commit from last year re-imported the DTS files form the upstream kernel.
> By doing so the VDD_LOG regulator in the board's DTS was dropped.
> Let's restore this, but move it into the u-boot overlay to prevent this
> issue in the future.
>
> Fixes: 167efc2c7a46 ("arm64: dts: rk3399: Sync v5.7-rc1 from Linux")
> Signed-off-by: Christoph Muellner <christoph.muellner@theobroma-systems.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> ---
>
> arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi b/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi
> index e7a1aea3a56..e0476ab25c9 100644
> --- a/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi
> +++ b/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi
> @@ -48,6 +48,18 @@
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
> };
> +
> + vdd_log: vdd-log {
> + compatible = "pwm-regulator";
> + pwms = <&pwm2 0 25000 1>;
> + regulator-name = "vdd_log";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <800000>;
> + regulator-max-microvolt = <1400000>;
> + regulator-init-microvolt = <950000>;
> + vin-supply = <&vcc5v0_sys>;
> + };
> };
>
> &gpio1 {
>
prev parent reply other threads:[~2021-02-19 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 0:29 [PATCH] rockchip: rk3399-puma: Restore correct VDD_LOG supply Christoph Muellner
2021-02-19 10:14 ` Heiko Stuebner [this message]
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=4319939.GKX7oQKdZx@diego \
--to=heiko.stuebner@theobroma-systems.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.