Arizona Regulator Updates v6
Subsystems (4)
cover Arizona Regulator Updates v6
Hi,
This series of patches are small fixes/improvements to the Arizona regulators. The main thing added is proper device tree bindings for getting the regulator init_data.
Changes Since v5:
- Use IS_ENABLED rather than ifdef for OF specific code
- Tidy up arizona_of_get_named_gpio base on comments by Lee Jones
Thanks,
Charles
Charles Keepax (6):
mfd: arizona: Factor out read of device tree GPIOs
regulator: arizona-ldo1: Move setup processing from arizona-core
regulator: arizona-ldo1: Add processing of init_data from device tree
mfd: arizona: Update DT binding to support LDO1 init_data
regulator: arizona-micsupp: Add processing of init_data from device
tree
mfd: arizona: Update DT binding to support MICVDD init_data
Documentation/devicetree/bindings/mfd/arizona.txt | 10 ++++ drivers/mfd/arizona-core.c | 41 +++++++++------ drivers/regulator/arizona-ldo1.c | 57 +++++++++++++++++++++ drivers/regulator/arizona-micsupp.c | 37 +++++++++++++ include/linux/mfd/arizona/core.h | 3 + 5 files changed, 131 insertions(+), 17 deletions(-)
Signature · 6 lines
1.7.2.5 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 1/6 mfd: arizona: Factor out read of device tree GPIOs
This patch factors out the reading of GPIOs for the Arizona devices into a helper function.
--- drivers/mfd/arizona-core.c | 31 ++++++++++++++++++++++--------- include/linux/mfd/arizona/core.h | 3 +++ 2 files changed, 25 insertions(+), 9 deletions(-)
drivers/mfd/arizona-core.c +22 -9
@@ -508,19 +508,32 @@ int arizona_of_get_type(struct device *dev) }EXPORT_SYMBOL_GPL (arizona_of_get_type); +int arizona_of_get_named_gpio (struct arizona *arizona,const char *prop, +bool mandatory) +{ +int gpio; + + gpio =of_get_named_gpio (arizona->dev->of_node, prop,0 ); +if (gpio <0 ) { +if (mandatory) +dev_err (arizona->dev, +"Mandatory DT gpio %s missing/malformed: %d\n" , + prop, gpio); + + gpio =0 ; + } + +return gpio; +} +EXPORT_SYMBOL_GPL (arizona_of_get_named_gpio); +static int arizona_of_get_core_pdata (struct arizona *arizona) { +struct arizona_pdata *pdata = &arizona->pdata;int ret, i; - arizona->pdata.reset =of_get_named_gpio (arizona->dev->of_node, -"wlf,reset" ,0 ); -if (arizona->pdata.reset <0 ) - arizona->pdata.reset =0 ; - - arizona->pdata.ldoena =of_get_named_gpio (arizona->dev->of_node, -"wlf,ldoena" ,0 ); -if (arizona->pdata.ldoena <0 ) - arizona->pdata.ldoena =0 ; + pdata->reset =arizona_of_get_named_gpio (arizona,"wlf,reset" , true); + pdata->ldoena =arizona_of_get_named_gpio (arizona,"wlf,ldoena" , true); ret = of_property_read_u32_array(arizona->dev->of_node, "wlf,gpio-defaults",
include/linux/mfd/arizona/core.h +3 -0
@@ -124,4 +124,7 @@ int wm5102_patch(struct arizona *arizona);int wm5110_patch (struct arizona *arizona);int wm8997_patch (struct arizona *arizona); +extern int arizona_of_get_named_gpio (struct arizona *arizona,const char *prop, +bool mandatory); +#endif
Signature · 1 line
1.7.2.5
Re: [PATCH 1/6] mfd: arizona: Factor out read of device tree GPIOs
Quoted 8 lines
This patch factors out the reading of GPIOs for the Arizona devices into a helper function.
--- drivers/mfd/arizona-core.c | 31 ++++++++++++++++++++++--------- include/linux/mfd/arizona/core.h | 3 +++ 2 files changed, 25 insertions(+), 9 deletions(-)
I'll wait for the rest of the patch-set to be ready before applying.
Signature · 8 lines
Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/6] mfd: arizona: Factor out read of device tree GPIOs
In reply to Charles KeepaxQuoted 2 lines · Charles Keepax
This patch factors out the reading of GPIOs for the Arizona devices into a helper function.
Applied, thanks.
PATCH 2/6 regulator: arizona-ldo1: Move setup processing from arizona-core
In reply to Charles KeepaxIt is more idiomatic to process things relating to the regulator in its driver. This patch moves both processing of device tree relating to the regulator and checking if the regulator is external from arizona-core into the regulator driver.
--- drivers/mfd/arizona-core.c | 12 +++--------- drivers/regulator/arizona-ldo1.c | 27 +++++++++++++++++++++++++++ 2 files changed, 30 insertions(+), 9 deletions(-)
drivers/mfd/arizona-core.c +3 -9
@@ -533,7 +533,6 @@ static int arizona_of_get_core_pdata(struct arizona *arizona)int ret, i; pdata->reset =arizona_of_get_named_gpio (arizona,"wlf,reset" , true); - pdata->ldoena =arizona_of_get_named_gpio (arizona,"wlf,ldoena" , true); ret = of_property_read_u32_array(arizona->dev->of_node, "wlf,gpio-defaults",
@@ -665,6 +664,9 @@ int arizona_dev_init(struct arizona *arizona)return -EINVAL ; } +/* Mark DCVDD as external, LDO1 driver will clear if internal */ + arizona->external_dcvdd = true; + ret =mfd_add_devices (arizona->dev,-1 , early_devs,ARRAY_SIZE (early_devs),NULL ,0 ,NULL );if (ret !=0 ) {
@@ -864,14 +866,6 @@ int arizona_dev_init(struct arizona *arizona) arizona->pdata.gpio_defaults[i]); } -/* -* LDO1 can only be used to supply DCVDD so if it has no -* consumers then DCVDD is supplied externally. -*/ -if (arizona->pdata.ldo1 && - arizona->pdata.ldo1->num_consumer_supplies ==0 ) - arizona->external_dcvdd = true; -pm_runtime_set_autosuspend_delay (arizona->dev,100 );pm_runtime_use_autosuspend (arizona->dev);pm_runtime_enable (arizona->dev);
drivers/regulator/arizona-ldo1.c +27 -0
@@ -178,6 +178,15 @@ static const struct regulator_init_data arizona_ldo1_default = { .num_consumer_supplies = 1, }; +static int arizona_ldo1_of_get_pdata (struct arizona *arizona) +{ +struct arizona_pdata *pdata = &arizona->pdata; + + pdata->ldoena =arizona_of_get_named_gpio (arizona,"wlf,ldoena" , true); + +return 0 ; +} +static int arizona_ldo1_probe (struct platform_device *pdev) {struct arizona *arizona =dev_get_drvdata (pdev->dev.parent);
@@ -186,6 +195,8 @@ static int arizona_ldo1_probe(struct platform_device *pdev)struct arizona_ldo1 *ldo1;int ret; + arizona->external_dcvdd = false; + ldo1 =devm_kzalloc (&pdev->dev,sizeof (*ldo1),GFP_KERNEL );if (!ldo1)return -ENOMEM ;
@@ -216,6 +227,15 @@ static int arizona_ldo1_probe(struct platform_device *pdev) config.dev = arizona->dev; config.driver_data = ldo1; config.regmap = arizona->regmap; + +if (IS_ENABLED (CONFIG_OF )) { +if (!dev_get_platdata (arizona->dev)) { + ret =arizona_ldo1_of_get_pdata (arizona); +if (ret <0 ) +return ret; + } + } + config.ena_gpio = arizona->pdata.ldoena;if (arizona->pdata.ldo1)
@@ -223,6 +243,13 @@ static int arizona_ldo1_probe(struct platform_device *pdev)else config.init_data = &ldo1->init_data; +/* +* LDO1 can only be used to supply DCVDD so if it has no +* consumers then DCVDD is supplied externally. +*/ +if (config.init_data->num_consumer_supplies ==0 ) + arizona->external_dcvdd = true; + ldo1->regulator =devm_regulator_register (&pdev->dev, desc, &config);if (IS_ERR (ldo1->regulator)) { ret =PTR_ERR (ldo1->regulator);
Signature · 6 lines
1.7.2.5 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/6] regulator: arizona-ldo1: Move setup processing from arizona-core
Quoted 10 lines
It is more idiomatic to process things relating to the regulator in its driver. This patch moves both processing of device tree relating to the regulator and checking if the regulator is external from arizona-core into the regulator driver.
--- drivers/mfd/arizona-core.c | 12 +++--------- drivers/regulator/arizona-ldo1.c | 27 +++++++++++++++++++++++++++ 2 files changed, 30 insertions(+), 9 deletions(-)
For the MFD part:
Mark, do you want me to set up an MFD-Regulator IB for v3.16?
Signature · 8 lines
Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Mark Brown
maintainerRe: [PATCH 2/6] regulator: arizona-ldo1: Move setup processing from arizona-core
In reply to Charles KeepaxQuoted 4 lines · Charles Keepax
It is more idiomatic to process things relating to the regulator in its driver. This patch moves both processing of device tree relating to the regulator and checking if the regulator is external from arizona-core into the regulator driver.
Applied, thanks. It would have been helpful to say in the commit log how this avoid races if the regulator driver is modular - the MFD can't get as far as checking if the DCVDD supply is internal until the supply is satisfied so if it's being used the LDO must have loaded.
PATCH 3/6 regulator: arizona-ldo1: Add processing of init_data from device tree
In reply to Charles Keepax--- drivers/regulator/arizona-ldo1.c | 34 ++++++++++++++++++++++++++++++++-- 1 files changed, 32 insertions(+), 2 deletions(-)
drivers/regulator/arizona-ldo1.c +32 -2
@@ -19,6 +19,7 @@#include <linux/platform_device.h> #include <linux/regulator/driver.h> #include <linux/regulator/machine.h> +#include <linux/regulator/of_regulator.h> #include <linux/gpio.h> #include <linux/slab.h>
@@ -178,12 +179,39 @@ static const struct regulator_init_data arizona_ldo1_default = { .num_consumer_supplies = 1, }; -static int arizona_ldo1_of_get_pdata (struct arizona *arizona) +static int arizona_ldo1_of_get_pdata (struct arizona *arizona, +struct regulator_config *config) {struct arizona_pdata *pdata = &arizona->pdata; +struct arizona_ldo1 *ldo1 = config->driver_data; +struct device_node *init_node, *dcvdd_node; +struct regulator_init_data *init_data; pdata->ldoena =arizona_of_get_named_gpio (arizona,"wlf,ldoena" , true); + init_node =of_get_child_by_name (arizona->dev->of_node,"ldo1" ); + dcvdd_node =of_parse_phandle (arizona->dev->of_node,"DCVDD-supply" ,0 ); + +if (init_node) { + config->of_node = init_node; + + init_data =of_get_regulator_init_data (arizona->dev, init_node); + +if (init_data) { + init_data->consumer_supplies = &ldo1->supply; + init_data->num_consumer_supplies =1 ; + +if (dcvdd_node && dcvdd_node != init_node) + arizona->external_dcvdd = true; + + pdata->ldo1 = init_data; + } + }else if (dcvdd_node) { + arizona->external_dcvdd = true; + } + +of_node_put (dcvdd_node); +return 0 ; }
@@ -230,7 +258,7 @@ static int arizona_ldo1_probe(struct platform_device *pdev)if (IS_ENABLED (CONFIG_OF )) {if (!dev_get_platdata (arizona->dev)) { - ret =arizona_ldo1_of_get_pdata (arizona); + ret =arizona_ldo1_of_get_pdata (arizona, &config);if (ret <0 )return ret; }
@@ -258,6 +286,8 @@ static int arizona_ldo1_probe(struct platform_device *pdev)return ret; } +of_node_put (config.of_node); +platform_set_drvdata (pdev, ldo1);return 0 ;
Signature · 1 line
1.7.2.5
Re: [PATCH 3/6] regulator: arizona-ldo1: Add processing of init_data from device tree
Quoted 1 line · Charles Keepax
Applied, but again you really need better changelogs - processing of init_data for what? For most regulators init_data is handled totally transparently so this isn't normal.
PATCH 4/6 mfd: arizona: Update DT binding to support LDO1 init_data
In reply to Charles Keepax--- Documentation/devicetree/bindings/mfd/arizona.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
Documentation/devicetree/bindings/mfd/arizona.txt +8 -0
@@ -42,6 +42,14 @@ Optional properties: the chip default will be used. If present exactly five values must be specified. + - DCVDD-supply : Power supply, only needs to be specified if DCVDD is being + externally supplied. As covered in + Documentation/devicetree/bindings/regulator/regulator.txt + +Optional subnodes: + - ldo1 : Initial data for the LDO1 regulator, as covered in + Documentation/devicetree/bindings/regulator/regulator.txt + Example: codec: wm5102@1a {
Signature · 1 line
1.7.2.5
PATCH 5/6 regulator: arizona-micsupp: Add processing of init_data from device tree
In reply to Charles Keepax--- drivers/regulator/arizona-micsupp.c | 37 +++++++++++++++++++++++++++++++++++ 1 files changed, 37 insertions(+), 0 deletions(-)
drivers/regulator/arizona-micsupp.c +37 -0
@@ -19,6 +19,7 @@#include <linux/platform_device.h> #include <linux/regulator/driver.h> #include <linux/regulator/machine.h> +#include <linux/regulator/of_regulator.h> #include <linux/gpio.h> #include <linux/slab.h> #include <linux/workqueue.h>
@@ -195,6 +196,32 @@ static const struct regulator_init_data arizona_micsupp_ext_default = { .num_consumer_supplies = 1, }; +static int arizona_micsupp_of_get_pdata (struct arizona *arizona, +struct regulator_config *config) +{ +struct arizona_pdata *pdata = &arizona->pdata; +struct arizona_micsupp *micsupp = config->driver_data; +struct device_node *np; +struct regulator_init_data *init_data; + + np =of_get_child_by_name (arizona->dev->of_node,"micvdd" ); + +if (np) { + config->of_node = np; + + init_data =of_get_regulator_init_data (arizona->dev, np); + +if (init_data) { + init_data->consumer_supplies = &micsupp->supply; + init_data->num_consumer_supplies =1 ; + + pdata->micvdd = init_data; + } + } + +return 0 ; +} +static int arizona_micsupp_probe (struct platform_device *pdev) {struct arizona *arizona =dev_get_drvdata (pdev->dev.parent);
@@ -234,6 +261,14 @@ static int arizona_micsupp_probe(struct platform_device *pdev) config.driver_data = micsupp; config.regmap = arizona->regmap; +if (IS_ENABLED (CONFIG_OF )) { +if (!dev_get_platdata (arizona->dev)) { + ret =arizona_micsupp_of_get_pdata (arizona, &config); +if (ret <0 ) +return ret; + } + } +if (arizona->pdata.micvdd) config.init_data = arizona->pdata.micvdd;else
@@ -253,6 +288,8 @@ static int arizona_micsupp_probe(struct platform_device *pdev)return ret; } +of_node_put (config.of_node); +platform_set_drvdata (pdev, micsupp);return 0 ;
Signature · 1 line
1.7.2.5
Mark Brown
maintainerRe: [PATCH 5/6] regulator: arizona-micsupp: Add processing of init_data from device tree
Quoted 1 line · Charles Keepax
Same here, you should have said what this is actually supposed to do.
PATCH 6/6 mfd: arizona: Update DT binding to support MICVDD init_data
In reply to Charles Keepax--- Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/mfd/arizona.txt +4 -2
@@ -42,13 +42,15 @@ Optional properties: the chip default will be used. If present exactly five values must be specified. - - DCVDD-supply : Power supply, only needs to be specified if DCVDD is being - externally supplied. As covered in + - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if + they are being externally supplied. As covered in Documentation/devicetree/bindings/regulator/regulator.txt Optional subnodes: - ldo1 : Initial data for the LDO1 regulator, as covered in Documentation/devicetree/bindings/regulator/regulator.txt + - micvdd : Initial data for the MICVDD regulator, as covered in + Documentation/devicetree/bindings/regulator/regulator.txt Example:
Signature · 1 line
1.7.2.5