22 Aug, 2020
1 commit
-
Fix below warning when CONFIG_OF=n:
drivers/regulator/fan53555.c:439:34: warning: ‘fan53555_dt_ids’ defined but not used [-Wunused-const-variable=]
439 | static const struct of_device_id fan53555_dt_ids[] = {
| ^~~~~~~~~~~~~~~Signed-off-by: Jisheng Zhang
Link: https://lore.kernel.org/r/20200821111324.430fe1da@xhacker.debian
Signed-off-by: Mark Brown
07 Nov, 2019
1 commit
-
SYR83X is used in Rockpro64 and it has die ID == 9. All other
registers are the same as in SYR82XSigned-off-by: Vasily Khoruzhick
Link: https://lore.kernel.org/r/20191106161211.1700663-1-anarsoul@gmail.com
Signed-off-by: Mark Brown
26 Apr, 2019
2 commits
-
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
The *regmap and *rdev can be replaced by local variables.
The slew_rate is no longer used since commit dd7e71fbeefe
("regulator: fan53555: use set_ramp_delay to set the ramp up slew rate").Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
26 Feb, 2019
1 commit
-
Current code does not really avoid array access out of bounds,
fix it by add checking for pdata->slew_rate.
If pdata->slew_rate is too big, it's a bug in pdata that needs fix.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
21 Feb, 2019
1 commit
-
The FAN53526 differs from the FAN53555 only in that the mode bit in
VSEL0/VSEL1 is moved to the CONTROL register, the voltage selector mask
is extended by 1 bit and the step is different.So extend the existing fan53555 driver to support FAN53526 as well.
Signed-off-by: Bjorn Andersson
Signed-off-by: Mark Brown
21 Aug, 2017
1 commit
-
The device tree nodes all correctly describe the regulators as
syr827 or syr828, but the I2C device id is currently set to the
wildcard value of syr82x in the driver. This causes udev to fail
to match the driver module with the modalias data from sysfs.Fix this by replacing the I2C device ids with ones that match the
device tree descriptions, with syr827 and syr828. Tested on
Firefly rk3288 board. The syr82x id was not used anywhere.Fixes: e80c47bd738b (regulator: fan53555: Export I2C module alias information)
Signed-off-by: Guillaume Tucker
Signed-off-by: Mark Brown
20 Jul, 2017
1 commit
-
if fan53555_regulator_probe() is called and the "client->dev.of_node"
isn't NULL, it means OF registered a device with a valid compatible
string, so match cannot be NULL.Use of_device_get_match_data() to retrieve the drvdata pointer. No
functional change intended.Signed-off-by: Jisheng Zhang
Signed-off-by: Mark Brown
01 Feb, 2017
1 commit
-
Declare regulator_ops structure as const as it is only stored in the ops
field of a regulator_desc structure. This field is of type const, so
regulator_ops structures having this property can be made const too.File size before: drivers/regulator/fan53555.o
text data bss dec hex filename
3512 496 8 4016 fb0 drivers/regulator/fan53555.oFile size after: drivers/regulator/fan53555.o
text data bss dec hex filename
3768 240 8 4016 fb0 drivers/regulator/fan53555.oSigned-off-by: Bhumika Goyal
Signed-off-by: Mark Brown
20 Apr, 2016
2 commits
-
IC type options 00, 13 and 23 are sharing the same DIE_ID 0.
Let's differentiate between these revisions.
FAN53555UC13X has the ID 0 and REV 0xf, starts at 800mV and
increments in 10mV steps.Signed-off-by: Wadim Egorov
Signed-off-by: Mark Brown -
FAN53555BUC18X has the DIE_ID 8, starts at 600mV and
increments in 10mV steps.Signed-off-by: Wadim Egorov
Signed-off-by: Mark Brown
16 Jan, 2016
1 commit
-
Setting the set_suspend_enable/disable callback to support
enable and disable the dcdc when system is suspend.Signed-off-by: zhangqing
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Mark Brown
01 Aug, 2015
1 commit
-
The I2C core always reports the MODALIAS uevent as "i2c:
Signed-off-by: Mark Brown
27 May, 2015
1 commit
-
Setting the set_voltage_time_sel callback to the standard function
regulator_set_voltage_time_sel enables the regulator to actually honor
ramp-delays when during regulator_set_voltage calls.Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown
06 Jan, 2015
1 commit
-
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const. Make const also
slew_rates array.Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Mark Brown
27 Nov, 2014
1 commit
-
The of_get_regulator_init_data() function is used to extract the regulator
init_data but information on how to extract certain data is defined in the
static regulator descriptor (e.g: how to map the hardware operating modes).Add a const struct regulator_desc * parameter to the function signature so
the parsing logic could use the information in the struct regulator_desc.of_get_regulator_init_data() relies on of_get_regulation_constraints() to
actually extract the init_data so it has to pass the struct regulator_desc
but that is modified on a later patch.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Mark Brown
19 Sep, 2014
2 commits
-
Set di->regulator before dereference it.
Signed-off-by: Axel Lin
Reviewed-by: Heiko Stuebner
Signed-off-by: Mark Brown -
Signed-off-by: Axel Lin
Reviewed-by: Heiko Stuebner
Signed-off-by: Mark Brown
18 Sep, 2014
1 commit
-
The vendor-id gathered from the dt match-data was cast to int but assigned
to an unsigned long, producing warnings on at least sparc, likedrivers/regulator/fan53555.c: In function 'fan53555_regulator_probe':
>> drivers/regulator/fan53555.c:373:16: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
di->vendor = (int) match->data;Fix this by using an appropriate cast.
Reported-by: kbuild test robot
Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown
17 Sep, 2014
3 commits
-
Silergy SYR82x regulators share the exact same functionality and register layout
as the Fairchild FAN53555 regulators. Therefore extend the driver to add
support for them.Both types use the same vendor id in their ID1 register, so it's not possible
to distinguish them automatically.Similarly, the types also do not match. Type 8 used by the SYR827 and SYR828
start at 712.5mV and increment in 12.5mv steps, while the FAN53555 type 8
starts at 600mV and increments in 10mV steps.Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown -
Add the ability to parse regulator-data from the devicetree.
Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown -
The regulator constraints already provide a field for the ramp_delay, so
there is no need to set this manually. Therefore implement the set_ramp_delay
callback and convert the pdata value to the constraint value if necessary.Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown
16 Sep, 2014
1 commit
-
The regulator can be supplied by a parent regulator through its vin pin,
so add the supply_name for it.Signed-off-by: Heiko Stuebner
Signed-off-by: Mark Brown
20 Feb, 2014
2 commits
-
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat
Cc: Yunfan Zhang
Signed-off-by: Mark Brown -
Propagate the error values returned by the function instead.
Signed-off-by: Sachin Kamat
Signed-off-by: Mark Brown
17 Sep, 2013
1 commit
-
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
05 Sep, 2013
1 commit
-
Pull PTR_RET() removal patches from Rusty Russell:
"PTR_RET() is a weird name, and led to some confusing usage. We ended
up with PTR_ERR_OR_ZERO(), and replacing or fixing all the usages.This has been sitting in linux-next for a whole cycle"
[ There are still some PTR_RET users scattered about, with some of them
possibly being new, but most of them existing in Rusty's tree too. We
have that#define PTR_RET(p) PTR_ERR_OR_ZERO(p)
thing in , so they continue to work for now - Linus ]
* tag 'PTR_RET-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux:
GFS2: Replace PTR_RET with PTR_ERR_OR_ZERO
Btrfs: volume: Replace PTR_RET with PTR_ERR_OR_ZERO
drm/cma: Replace PTR_RET with PTR_ERR_OR_ZERO
sh_veu: Replace PTR_RET with PTR_ERR_OR_ZERO
dma-buf: Replace PTR_RET with PTR_ERR_OR_ZERO
drivers/rtc: Replace PTR_RET with PTR_ERR_OR_ZERO
mm/oom_kill: remove weird use of ERR_PTR()/PTR_ERR().
staging/zcache: don't use PTR_RET().
remoteproc: don't use PTR_RET().
pinctrl: don't use PTR_RET().
acpi: Replace weird use of PTR_RET.
s390: Replace weird use of PTR_RET.
PTR_RET is now PTR_ERR_OR_ZERO(): Replace most.
PTR_RET is now PTR_ERR_OR_ZERO
30 Jul, 2013
1 commit
-
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.Signed-off-by: Jingoo Han
Signed-off-by: Mark Brown
15 Jul, 2013
1 commit
-
Sweep of the simple cases.
Cc: netdev@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: Julia Lawall
Signed-off-by: Rusty Russell
Acked-by: David S. Miller
Acked-by: Benjamin Herrenschmidt
20 Mar, 2013
1 commit
-
Used PTR_RET function instead of IS_ERR and PTR_ERR.
Patch found using coccinelle.Signed-off-by: Alexandru Gheorghiu
Signed-off-by: Mark Brown
20 Nov, 2012
3 commits
-
CONFIG_HOTPLUG is going away as an option so __devexit is no
longer needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown -
CONFIG_HOTPLUG is going away as an option so __devinit is no longer
needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown -
CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown
10 Sep, 2012
2 commits
-
The max voltage will be bounded by min_uV, uV_step and n_voltages, so
remove it to avoid confusing.Signed-off-by: Yunfan Zhang
Reviewed-by: Axel Lin
Signed-off-by: Mark Brown -
This driver supports Fairchild FAN53555 Digitally Programmable
TinyBuck Regulator. The FAN53555 is a step-down switching voltage
regulator that delivers a digitally programmable output from an
input voltage supply of 2.5V to 5.5V. The output voltage is
programmed through an I2C interface.Signed-off-by: Yunfan Zhang
Signed-off-by: Mark Brown
