u-boot.git/drivers/power, branch v2026.04

power: regulator: qcom: Correct dependenecies for DM_REGULATOR_QCOM_USB_VBUS

2026-03-24T10:42:19Z

The DM_REGULATOR_QCOM_USB_VBUS functionality can only work with DM_PMIC enabled as well, so express this dependency in Kconfig. Signed-off-by: Tom Rini Link: https://patch.msgid.link/20260323195302.2363577-1-trini@konsulko.com Signed-off-by: Casey Connolly

power: domain: Validate device tree node in dev_power_domain_ctrl

2026-02-26T15:04:46Z

Similar to pinctrl_select_state(), add dev_has_ofnode() check before doing the real work. Device(scmi_base.0) does not have a real device node, ofnode_null() is assigned as the device tree node for scmi base protocol device: 'commit 7eb4eb541c14 ("firmware: scmi: install base protocol to SCMI agent")' However with recent update in 'commit 0535e46d55d7 ("scripts/dtc: Update to upstream version v1.7.2-35-g52f07dcca47c")', SPL panic in fdt_check_node_offset_()->fdt_next_tag(), because offset is -1 and SPL_OF_LIBFDT_ASSUME_MASK is 0xFF. So need to validate device tree node. Reported-by: Ye Li Closes: https://lore.kernel.org/u-boot/939a9696-27fa-45a1-b428-feffe21ac6d5@oss.nxp.com/ Signed-off-by: Peng Fan

power: regulator: enable AWP318W SPL support

2026-01-25T23:29:32Z

Add the descriptions for the DC/DC regulators of the AXP318W, and enable it when CONFIG_AXP318W_POWER is enabled. Signed-off-by: Yixun Lan Reviewed-by: Andre Przywara

power: regulator: add AXP318W support

2026-01-25T23:29:32Z

The PMIC is also known as AXP819 in vendor pmu code For DCDC6, 8, 9, the underlying hardware support more than two levels voltage step tuning, but for now only first two levels are implemented in this driver, hence highest voltage will be limited at seccond level. It actual meets board requirement in current design, and we've verified it in Radxa Cubie A7A board. Following are detail explanation of voltage tuning stpes for those DCDCs: DCDC | voltage range | units | steps | implemented 6 | 0.5 - 1.2 | 10 mV | 71 | Y . | 1.22 - 1.54 | 20 mV | 17 | Y . | 1.8 - 2.4 | 20 mV | 31 | N . | 2.44 - 2.76 | 40 mV | 9 | N -------------------------------------------------- 8/9 | 0.5 - 1.2 | 10 mV | 71 | Y . | 1.22 - 1.84 | 20 mV | 32 | Y . | 1.9 - 3.4 | 100mV | 16 | N Signed-off-by: Yixun Lan Reviewed-by: Andre Przywara

power: regulator: common: fix compilation issue

2026-01-22T02:38:22Z

If CONFIG_DM_GPIO is not enabled, compilation fails with the following errors: aarch64-none-linux-gnu-ld: drivers/power/regulator/regulator_common.o: in function `regulator_common_of_to_plat': <...>/u-boot/drivers/power/regulator/regulator_common.c:30: undefined reference to `gpio_request_by_name' aarch64-none-linux-gnu-ld: drivers/power/regulator/regulator_common.o: in function `regulator_common_get_enable': <...>/u-boot/drivers/power/regulator/regulator_common.c:57: undefined reference to `dm_gpio_get_value' aarch64-none-linux-gnu-ld: drivers/power/regulator/regulator_common.o: in function `regulator_common_set_enable': <...>/u-boot/drivers/power/regulator/regulator_common.c:92: undefined reference to `dm_gpio_set_value' make: *** [Makefile:2029: u-boot] Error 139 Since the enable gpio is optional we can conditionally skip these calls. Reviewed-by: Tanmay Kathpalia Reviewed-by: Peng Fan Signed-off-by: Julien Stephan Reviewed-by: Quentin Schulz Signed-off-by: Peng Fan

power: regulator: common: use dm_gpio_is_valid helper

2026-01-22T02:01:10Z

Use dm_gpio_is_valid() helper function instead of manually checking the gpio. Reviewed-by: Peng Fan Reviewed-by: Tanmay Kathpalia Reviewed-by: Neil Armstrong Signed-off-by: Julien Stephan Signed-off-by: Peng Fan

power: regulator: common: remove unnecessary debug trace

2026-01-22T02:01:10Z

Drop the ftrace like debug() that checkpatch --strict complains about: WARNING: Unnecessary ftrace-like logging - prefer using ftrace Reviewed-by: Peng Fan Reviewed-by: Tanmay Kathpalia Reviewed-by: Neil Armstrong Signed-off-by: Julien Stephan Signed-off-by: Peng Fan

power: regulator: qcom-rpmh: correctly map pmic mode

2026-01-14T15:25:09Z

Currently we don't properly map between the regulator mode ID enum and the appropriate register values in the mode map, as a result we always unintentionally vote for retention mode if we actually attempt to set it. In the set_mode path we did find the appropriate entry in the mode map but we wrote the id instead of the register values. Clean this up and properly map id -> mode and vice versa. Link: https://patch.msgid.link/20260108-rpmh-regulator-fixes-v1-6-d1b5b300b665@linaro.org Signed-off-by: Casey Connolly

power: regulator: qcom-rpmh: read votes from rpmh

2026-01-14T15:25:09Z

Make use of the new RPMh read support to fetch regulator values that may have been voted on by a previous bootloader stage. This allows commands like "regulator status" to report the actual votes programmed into hardware (though not necessarily the actual states of the regulators once the votes have been aggregated). Link: https://patch.msgid.link/20260108-rpmh-regulator-fixes-v1-5-d1b5b300b665@linaro.org Signed-off-by: Casey Connolly

regulator: qcom-rpmh-regulator: add support for PM8150 PM8350 PM7325

2026-01-14T15:25:09Z

Add the PM8150, PM8350, and PM7325 regulator data found on Qualcomm platforms. These regulator tables are imported from the Linux driver to enable support for these PMICs in U-Boot. Signed-off-by: Aswin Murugan Reviewed-by: Neil Armstrong Link: https://patch.msgid.link/20251112164204.1557934-1-aswin.murugan@oss.qualcomm.com Signed-off-by: Casey Connolly