[PATCH v3 4/4] ARM: OMAP2+: ti81xx: use non-scalable voltage domains
From: Ettore Chimenti
Date: Fri Nov 13 2026 - 16:31:55 EST
TI81xx SoCs reuse omap3xxx_voltagedomains_init(), which registers the
OMAP34xx/36xx voltage domains for every SoC except AM35xx. Those
domains are marked scalable and reference OMAP3 Voltage Controller and
Voltage Processor instances, which do not exist on DM814x/DM816x, and
no PMIC data is registered for these SoCs either.
As a result, omap_voltage_late_init() tries to set them up on every
boot and bails out early with:
omap_voltage_late_init: Could not get sys clk.
Adding a "sys_ck" clock alias would only push the failure further into
omap_vc_init_channel() and omap_vp_init(), which then complain about
missing PMIC data.
TI81xx has no voltage scaling support in mainline, so, as done for
AM35xx in commit ddf536d0d7e1 ("ARM: OMAP: AM3517/3505: fix crash on
boot due to incorrect voltagedomain data"), register the non-scalable
voltage domains instead. They still provide the "mpu_iva", "core" and
"wkup" domains needed by the powerdomain data, and
omap_voltage_late_init() now skips them.
Signed-off-by: Ettore Chimenti <ettore.chimenti@xxxxxxxxxx>
---
arch/arm/mach-omap2/voltagedomains3xxx_data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/voltagedomains3xxx_data.c b/arch/arm/mach-omap2/voltagedomains3xxx_data.c
index e98a3f289c27..478f5eb2a17f 100644
--- a/arch/arm/mach-omap2/voltagedomains3xxx_data.c
+++ b/arch/arm/mach-omap2/voltagedomains3xxx_data.c
@@ -119,7 +119,7 @@ void __init omap3xxx_voltagedomains_init(void)
omap3_voltdm_mpu.vc_param = &omap3_mpu_vc_data;
omap3_voltdm_core.vc_param = &omap3_core_vc_data;
- if (soc_is_am35xx())
+ if (soc_is_am35xx() || soc_is_ti81xx())
voltdms = voltagedomains_am35xx;
else
voltdms = voltagedomains_omap3;
--
2.56.1