From: Quentin Schulz <quentin.schulz@cherry.de>
To: Chaoyi Chen <kernel@airkyi.com>,
Kever Yang <kever.yang@rock-chips.com>,
Tom Rini <trini@konsulko.com>, Jonas Karlman <jonas@kwiboo.se>
Cc: u-boot@lists.denx.de, Chaoyi Chen <chaoyi.chen@rock-chips.com>
Subject: Re: [PATCH] configs: rockchip: Enable RK806 PMIC on rk3588-evb
Date: Wed, 19 Nov 2025 10:52:50 +0100 [thread overview]
Message-ID: <bae11d52-65cf-4d8f-a51e-115a90a7444c@cherry.de> (raw)
In-Reply-To: <20251119015554.153-1-kernel@airkyi.com>
Hi Chaoyi Chen,
On 11/19/25 2:55 AM, Chaoyi Chen wrote:
> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>
> Some pmdomains rely on RK806 PMIC for power supply. If we don't
> enable them in U-Boot, random panic may occur during the Kernel
> boot process.
>
The kernel shouldn't rely on U-Boot doing something to work, so please
fix this with upstream Linux kernel.
Can you tell us what's the issue?
The issue with this patch here is that we probably would need **all**
RK3588 boards to have the PMIC enabled, and all the appropriate
regulators brought up before booting into the kernel. It'd be *much*
better this is fixed in Linux (and depending on what we're talking
about, it may need another fix in U-Boot so that whatever depends on the
PM domain works as well).
Also, why the PMIC in SPL but not the regulators?
Cheers,
Quentin
next prev parent reply other threads:[~2025-11-19 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 1:55 [PATCH] configs: rockchip: Enable RK806 PMIC on rk3588-evb Chaoyi Chen
2025-11-19 9:52 ` Quentin Schulz [this message]
2025-11-19 10:09 ` Chaoyi Chen
2025-11-19 10:45 ` Quentin Schulz
2025-11-20 3:05 ` Chaoyi Chen
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=bae11d52-65cf-4d8f-a51e-115a90a7444c@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=chaoyi.chen@rock-chips.com \
--cc=jonas@kwiboo.se \
--cc=kernel@airkyi.com \
--cc=kever.yang@rock-chips.com \
--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 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.