renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-11-30 05:25:20 +08:00
Code

regulator: axp20x: Use parent device as regulator configuration device

Browse Source 
The current device used for the regulator configuration is the child device
created by the MFD driver. This means that it doesn't have any of_node pointing
to it, and whenever we register the regulators, it will not look into the
regulator supply in the DT, hence requiring to provide regulator aliases in the
MFD driver.

We can easily fix that by using the parent device in our configuration, which
has a DT node associated to it, and will allow a DT lookup. Eventually, we will
be able to remove the aliases in the MFD driver.

Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
This commit is contained in:
Maxime Ripard 2014-09-20 22:06:34 +02:00 committed by Mark Brown
parent 7d1311b93e
commit 0d90ecf31e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/regulator/axp20x-regulator.c
View File

@ -245,7 +245,7 @@ static int axp20x_regulator_probe(struct platform_device *pdev)
for (i = 0; i < AXP20X_REG_ID_MAX; i++) { for (i = 0; i < AXP20X_REG_ID_MAX; i++) {
init_data = axp20x_matches[i].init_data; init_data = axp20x_matches[i].init_data;
config.dev = &pdev->dev; config.dev = pdev->dev.parent;
config.init_data = init_data; config.init_data = init_data;
config.regmap = axp20x->regmap; config.regmap = axp20x->regmap;
config.of_node = axp20x_matches[i].of_node; config.of_node = axp20x_matches[i].of_node;