Skip to contentSkip to conversation

regulator: set of_node for qcom vbus regulator

PATCH RESEND In review Jonathan Marek 2 participants 2 messages Aug 18, 2020

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH RESEND 1/1 regulator: set of_node for qcom vbus regulator

This allows the regulator to be found by devm_regulator_get().

Fixes 4fe66d5a62fb ("regulator: Add support for QCOM PMIC VBUS booster")
---
 drivers/regulator/qcom_usb_vbus-regulator.c | 1 +
 1 file changed, 1 insertion(+)
drivers/regulator/qcom_usb_vbus-regulator.c +1 -0
index 8ba947f3585f..457788b50572 100644
@@ -63,6 +63,7 @@ static int qcom_usb_vbus_regulator_probe(struct platform_device *pdev)
 	qcom_usb_vbus_rdesc.enable_mask = OTG_EN;
 	config.dev = dev;
 	config.init_data = init_data;
+	config.of_node = dev->of_node;
 	config.regmap = regmap;
 
 	rdev = devm_regulator_register(dev, &qcom_usb_vbus_rdesc, &config);
Signature · 1 line
2.26.1
maintainer
#1 lore raw
Quoted 3 lines · Jonathan Marek

This allows the regulator to be found by devm_regulator_get().

Fixes 4fe66d5a62fb ("regulator: Add support for QCOM PMIC VBUS booster")

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: set of_node for qcom vbus regulator

      commit: 66c3b96a7bd042427d2e0eaa8704536828f8235f

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark