From: Quentin Schulz <quentin.schulz@cherry.de>
To: Chris Morgan <macroalpha82@gmail.com>, u-boot@lists.denx.de
Cc: jonas@kwiboo.se, trini@konsulko.com, kever.yang@rock-chips.com,
philipp.tomsich@vrull.eu, sjg@chromium.org, dsimic@manjaro.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH V2 4/4] board: rockchip: Enable PD_VO before driver access
Date: Mon, 23 Sep 2024 13:24:34 +0200 [thread overview]
Message-ID: <da41ca54-871e-4e40-b7c8-626a3c4a3f1a@cherry.de> (raw)
In-Reply-To: <20240919140022.511067-5-macroalpha82@gmail.com>
Hi Chris,
On 9/19/24 4:00 PM, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Enable the PD_VO power domain before driver access on the rk3568 SoC.
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> ---
> arch/arm/mach-rockchip/rk3568/rk3568.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/mach-rockchip/rk3568/rk3568.c b/arch/arm/mach-rockchip/rk3568/rk3568.c
> index 1b3e40074e3..d5742b68d68 100644
> --- a/arch/arm/mach-rockchip/rk3568/rk3568.c
> +++ b/arch/arm/mach-rockchip/rk3568/rk3568.c
> @@ -26,6 +26,8 @@
> #define PMU_BASE_ADDR 0xfdd90000
> #define PMU_NOC_AUTO_CON0 (0x70)
> #define PMU_NOC_AUTO_CON1 (0x74)
> +#define PMU_PWR_GATE_SFTCON (0xa0)
> +#define PMU_PD_VO_DWN_ENA BIT(7)
> #define EDP_PHY_GRF_BASE 0xfdcb0000
> #define EDP_PHY_GRF_CON0 (EDP_PHY_GRF_BASE + 0x00)
> #define EDP_PHY_GRF_CON10 (EDP_PHY_GRF_BASE + 0x28)
> @@ -130,6 +132,10 @@ int arch_cpu_init(void)
> writel(0x3f3f0707, GRF_BASE + GRF_GPIO1C_DS_1);
> writel(0x3f3f0707, GRF_BASE + GRF_GPIO1C_DS_2);
> writel(0x3f3f0707, GRF_BASE + GRF_GPIO1C_DS_3);
> +
> + /* Enable VO power domain for display */
> + writel((PMU_PD_VO_DWN_ENA << 16),
> + PMU_BASE_ADDR + PMU_PWR_GATE_SFTCON);
Maybe we want to guard this with a symbol for video stuff in U-Boot? I
assume Linux is capable of handling this just fine without U-Boot's
intervention?
At the very least have #if CONFIG_IS_ENABLED(VIDEO) ?
What do you think?
Cheers,
Quentin
next prev parent reply other threads:[~2024-09-23 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 14:00 [PATCH V2 0/4] Anbernic RGxx3 Bootloader Fixes Chris Morgan
2024-09-19 14:00 ` [PATCH V2 1/4] board: rockchip: Convert Anbernic RGxx3 to OF_UPSTREAM Chris Morgan
2024-10-25 12:04 ` Kever Yang
2024-09-19 14:00 ` [PATCH V2 2/4] board: rockchip: Add vdd_cpu reg fixup for RGXX3 Series Chris Morgan
2024-09-23 11:21 ` Quentin Schulz
2024-09-23 17:36 ` Chris Morgan
2024-09-24 10:24 ` Quentin Schulz
2024-09-26 0:35 ` Chris Morgan
2024-10-25 12:04 ` Kever Yang
2024-09-19 14:00 ` [PATCH V2 3/4] board: rockchip: Remove ARM SCMI Support from RGxx3 Chris Morgan
2024-10-25 12:04 ` Kever Yang
2024-09-19 14:00 ` [PATCH V2 4/4] board: rockchip: Enable PD_VO before driver access Chris Morgan
2024-09-23 11:24 ` Quentin Schulz [this message]
2024-09-23 17:38 ` Chris Morgan
2024-09-24 9:19 ` Quentin Schulz
2024-09-26 0:23 ` Chris Morgan
2024-10-25 12:04 ` Kever Yang
2024-09-22 13:43 ` [PATCH V2 0/4] Anbernic RGxx3 Bootloader Fixes Peter Robinson
2024-09-23 17:42 ` 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=da41ca54-871e-4e40-b7c8-626a3c4a3f1a@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=dsimic@manjaro.org \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox