30 Aug, 2015
1 commit
-
…'regulator/topic/owner', 'regulator/topic/pfuze100' and 'regulator/topic/pwm' into regulator-next
29 Aug, 2015
1 commit
-
The driver has a I2C device id table that is used to create the modaliases
and also "pfuze100-regulator" is not a supported I2C id, so is never used.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Mark Brown
15 Jul, 2015
1 commit
-
i2c_driver does not need to set an owner because i2c_register_driver()
will set it.Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Mark Brown
09 Jan, 2015
1 commit
-
Add pfuze3000 chip support.
Signed-off-by: Robin Gong
Signed-off-by: Mark Brown
27 May, 2014
1 commit
-
Current code has .enable_reg and .enable_mask settings, but the implementation
for corresponding callbacks are missing. Fix it.Signed-off-by: Axel Lin
Tested-by: Robin Gong
Acked-by: Robin Gong
Signed-off-by: Mark Brown
26 May, 2014
2 commits
-
Previously, the PFUZE100 would try to allocate gpio0 io0 because
config.ena_gpio defaults to 0, which can be a valid GPIO. To prevent this
from happening, set this parameter to -EINVAL.Signed-off-by: Sean Cross
Signed-off-by: Mark Brown -
The SWB regulators have the ability to be turned on and off. Add
enable/disable support for these regulators.Signed-off-by: Sean Cross
Signed-off-by: Mark Brown
27 Mar, 2014
1 commit
-
…97', 'regulator/topic/max8998', 'regulator/topic/mc13xxx', 'regulator/topic/pfuze100', 'regulator/topic/rc5t583' and 'regulator/topic/s2mps11' into regulator-next
06 Mar, 2014
1 commit
-
Signed-off-by: Axel Lin
Acked-by: Robin Gong
Signed-off-by: Mark Brown
04 Mar, 2014
2 commits
-
Also remove PFUZE_NUM to avoid below build warnings:
CC [M] drivers/regulator/pfuze100-regulator.o
drivers/regulator/pfuze100-regulator.c:86:2: warning: excess elements in array initializer [enabled by default]
drivers/regulator/pfuze100-regulator.c:86:2: warning: (near initialization for 'pfuze_device_id') [enabled by default]
drivers/regulator/pfuze100-regulator.c:93:2: warning: excess elements in array initializer [enabled by default]
drivers/regulator/pfuze100-regulator.c:93:2: warning: (near initialization for 'pfuze_dt_ids') [enabled by default]Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
support pfuze200 chip which remove SW1C and SW4 based on pfuze100.
Signed-off-by: Robin Gong
Signed-off-by: Mark Brown
23 Feb, 2014
1 commit
-
If of_node_get() fails, we should return an error.
Signed-off-by: Fabio Estevam
Signed-off-by: Mark Brown
19 Feb, 2014
1 commit
-
Since commit d7857c42 (regulator: pfuze100: Use of_get_child_by_name) we get
the following probe failure:pfuze100-regulator 1-0008: Full layer: 1, Metal layer: 0
pfuze100-regulator 1-0008: FAB: 0, FIN: 0
pfuze100-regulator 1-0008: regulators node not found
pfuze100-regulator: probe of 1-0008 failed with error -22Now that of_get_child_by_name() is used we should adjust the device_node pointer
'np' to not get the parent node anymore.Suggested-by: Shawn Guo
Signed-off-by: Fabio Estevam
Acked-by: Sachin Kamat
Signed-off-by: Mark Brown
15 Feb, 2014
1 commit
-
of_find_node_by_name walks the allnodes list, and can thus walk
outside of the parent node. Use of_get_child_by_name instead.Signed-off-by: Sachin Kamat
Signed-off-by: Mark Brown
03 Feb, 2014
1 commit
-
Signed-off-by: Thiago Farina
Signed-off-by: Mark Brown
23 Jan, 2014
2 commits
-
… 'regulator/topic/lp3971', 'regulator/topic/lp3972', 'regulator/topic/max14577', 'regulator/topic/max77693', 'regulator/topic/mc13892', 'regulator/topic/pcf50633' and 'regulator/topic/pfuze100' into regulator-linus
-
'lay' is not very meaningful, so use it 'layer' instead to let the dev_info()
clearer.Signed-off-by: Fabio Estevam
Signed-off-by: Mark Brown
15 Jan, 2014
2 commits
-
Fix the following checkpatch error and warning:
ERROR: switch and case should be at the same indent
#311: FILE: drivers/regulator/pfuze100-regulator.c:311:
+ switch (value & 0x0f) {
[...]
+ case 0x8:
[...]
+ case 0x0:
[...]
+ default:WARNING: line over 80 characters
#312: FILE: drivers/regulator/pfuze100-regulator.c:312:
+ /* Freescale misprogrammed 1-3% of parts prior to week 8 of 2013 as ID=8 */Signed-off-by: Fabio Estevam
Signed-off-by: Mark Brown -
Linux 3.13-rc4
10 Dec, 2013
3 commits
-
Use devm_regulator_register() to make cleanup paths simpler,
and remove unnecessary remove().Signed-off-by: Jingoo Han
Acked-by: Robin Gong
Signed-off-by: Mark Brown -
prior to week 08 of 2013 Freescale misprogrammed between 1 and 3% of
PFUZE1000 parts with a ID=0x8 instead of the expected ID=0x0Signed-off-by: Tim Harvey
Signed-off-by: Mark Brown
Cc: stable@vger.kernel.org -
According to the datasheet, the address of FABID is 0x4. Fix it.
Signed-off-by: Axel Lin
Acked-by: Robin Gong
Signed-off-by: Mark Brown
Cc: stable@vger.kernel.org
02 Aug, 2013
1 commit
-
max_register should be register count - 1.
Signed-off-by: Axel Lin
Reviewed-by: Robin Gong
Signed-off-by: Mark Brown
01 Aug, 2013
1 commit
-
Simplify the equation to calculate ramp_delay.
Below equations are equivalent:
ramp_delay = 25000 / (2 * ramp_delay);
ramp_delay = 50000 / (4 * ramp_delay);
ramp_delay = 25000 / (2 * ramp_delay);
ramp_delay = 12500 / ramp_delay;
So we don't need to read BIT6 of rdev->desc->vsel_reg for applying different
equations.Also use rdev->desc->vsel_reg instead of run-time calculate register address.
Signed-off-by: Axel Lin
Reviewed-by: Robin Gong
Signed-off-by: Mark Brown
30 Jul, 2013
1 commit
-
Current code adjust min_uV and uV_step but missed adjusting the n_voltages
setting.When BIT6 is clear:
n_voltages = (1975000 - 400000) / 25000 + 1 = 64
When BIT6 is set:
n_voltages = (3300000 - 800000) / 50000 + 1 = 51The n_voltages needs update because when BIT6 is set 0x73 ~ 0x7f are reserved.
When using regulator_list_voltage_linear, the n_voltages does matter here
because wrong n_voltages setting make the equation return wrong result.
e.g. if selector is 63, regulator_list_voltage_linear returns
800000 + (50000 * 63) = 4000000
It should return -EINVAL if the selector is in the range of 51 ~ 63.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
29 Jul, 2013
4 commits
-
All table based voltage list have ascendant order.
Use regulator_map_voltage_ascend for them.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
i2c drivers use "i2c:" prefix for module alias.
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Since this is a i2c driver, use i2c_[set|get]_clientdata instead of
dev_[set|get]_drvdata.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Fix building error on x86_64 and i386:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/regulator/pfuze100-regulator.oSigned-off-by: Robin Gong
Signed-off-by: Mark Brown
27 Jul, 2013
1 commit
-
fix building warning and correct the binding doc
Signed-off-by: Robin Gong
Signed-off-by: Mark Brown
25 Jul, 2013
1 commit
-
Add pfuze100 regulator driver.
Signed-off-by: Robin Gong
Tested-by: Steffen Trumtrar
Signed-off-by: Mark Brown