On Thu, Jun 18, 2026 at 7:01 AM Linus Walleij <[email protected]> wrote:
>
> Add a DB8500 regulator driver for the VAPE and VSMPS2 compatibility nodes.
>
> Back the regulator enable state with the corresponding power domains.
>
> This is done for off-chip consumers: the corresponding voltage rails are
> routed out so they are used for powering different peripherals using
> these voltages as supplies.
>
> Assisted-by: Codex:gpt-5-5
> Signed-off-by: Linus Walleij <[email protected]>
> ---
> arch/arm/boot/dts/st/ste-dbx5x0.dtsi | 2 +
> drivers/regulator/Kconfig | 11 ++
> drivers/regulator/Makefile | 1 +
> drivers/regulator/db8500-regulator.c | 221
> +++++++++++++++++++++++++++++++++++
> 4 files changed, 235 insertions(+)
>
> diff --git a/arch/arm/boot/dts/st/ste-dbx5x0.dtsi
> b/arch/arm/boot/dts/st/ste-dbx5x0.dtsi
> index a6fef302c994..fd6a075e4c93 100644
> --- a/arch/arm/boot/dts/st/ste-dbx5x0.dtsi
> +++ b/arch/arm/boot/dts/st/ste-dbx5x0.dtsi
> @@ -673,6 +673,7 @@ db8500-prcmu-regulators {
> // DB8500_REGULATOR_VAPE
> db8500_vape_reg: db8500_vape {
> regulator-always-on;
> + power-domains = <&pm_domains
> DOMAIN_VAPE>;
Hmm, isn't this the other way around? The power-domains node should
have a regulator supply?
We may even consider to skip to model the regulator altogether and
make the power domain operate directly on the prcmu instead.
> };
>
> // DB8500_REGULATOR_VARM
> @@ -693,6 +694,7 @@ db8500_vsmps1_reg: db8500_vsmps1 {
>
> // DB8500_REGULATOR_VSMPS2
> db8500_vsmps2_reg: db8500_vsmps2 {
> + power-domains = <&pm_domains
> DOMAIN_VSMPS2>;
Ditto.
> };
>
> // DB8500_REGULATOR_VSMPS3
> diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
> index acc698c17bd2..8db63d8d3fa4 100644
> --- a/drivers/regulator/Kconfig
> +++ b/drivers/regulator/Kconfig
> @@ -397,6 +397,17 @@ config REGULATOR_DA9210
> converter 12A DC-DC Buck controlled through an I2C
> interface.
>
[...]
Kind regards
Uffe
