linux-toradex.git/drivers/regulator/wm831x-dcdc.c, branch v7.0-rc2

regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in 4.14

2023-03-20T13:11:25+00:00

Probing of regulators can be a slow operation and can contribute to
slower boot times. This is especially true if a regulator is turned on
at probe time (with regulator-boot-on or regulator-always-on) and the
regulator requires delays (off-on-time, ramp time, etc).

While the overall kernel is not ready to switch to async probe by
default, as per the discussion on the mailing lists [1] it is believed
that the regulator subsystem is in good shape and we can move
regulator drivers over wholesale. There is no way to just magically
opt in all regulators (regulators are just normal drivers like
platform_driver), so we set PROBE_PREFER_ASYNCHRONOUS for all
regulators found in 'drivers/regulator' individually.

Given the number of drivers touched and the impossibility to test this
ahead of time, it wouldn't be shocking at all if this caused a
regression for someone. If there is a regression caused by this patch,
it's likely to be one of the cases talked about in [1]. As a "quick
fix", drivers involved in the regression could be fixed by changing
them to PROBE_FORCE_SYNCHRONOUS. That being said, the correct fix
would be to directly fix the problem that caused the issue with async
probe.

The approach here follows a similar approach that was used for the mmc
subsystem several years ago [2]. In fact, I ran nearly the same python
script to auto-generate the changes. The only thing I changed was to
search for "i2c_driver", "spmi_driver", and "spi_driver" in addition
to "platform_driver".

[1] https://lore.kernel.org/r/06db017f-e985-4434-8d1d-02ca2100cca0@sirena.org.uk
[2] https://lore.kernel.org/r/20200903232441.2694866-1-dianders@chromium.org/

Signed-off-by: Douglas Anderson
Link: https://lore.kernel.org/r/20230316125351.1.I2a4677392a38db5758dee0788b2cea5872562a82@changeid
Signed-off-by: Mark Brown

regulator: remove locking around regulator_notifier_call_chain()

2020-09-07T17:35:25+00:00

regulator_notifier_call_chain() doesn't need rdev lock and rdev's
existence is assumed in the code anyway. Remove the locks from drivers.

Signed-off-by: Michał Mirosław 
Acked-by: Adam Thomson 
Reviewed-by: Dmitry Osipenko 
Link: https://lore.kernel.org/r/42393f66dcc4d80dcd9797be45216b4035aa96cb.1597032945.git.mirq-linux@rere.qmqm.pl
Signed-off-by: Mark Brown

regulator: use linear_ranges helper

2020-05-08T17:18:13+00:00

Change the regulator helpers to use common linear_ranges code.

Signed-off-by: Matti Vaittinen 
Reviewed-by: Mark Brown 
Acked-by: Charles Keepax 
Acked-by: Adam Thomson 
Link: https://lore.kernel.org/r/64f01d5e381b8631a271616b7790f9d5640974fb.1588944082.git.matti.vaittinen@fi.rohmeurope.com
Signed-off-by: Mark Brown

regulator: wm831x: Convert to use GPIO descriptors

2019-06-12T12:59:11+00:00

This converts the Wolfson Micro WM831x DCDC converter to use
a GPIO descriptor for the GPIO driving the DVS pin.

There is just one (non-DT) machine in the kernel using this, and
that is the Wolfson Micro (now Cirrus) Cragganmore 6410 so we
patch this board to pass a descriptor table and fix up the driver
accordingly.

Cc: Charles Keepax 
Cc: Richard Fitzgerald 
Cc: patches@opensource.cirrus.com
Signed-off-by: Linus Walleij 
Acked-by: Charles Keepax 
Signed-off-by: Mark Brown

regulator: wm831x: Switch to SPDX identifier

2019-04-17T16:40:29+00:00

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: wm831x: Fix notifier mutex lock warning

2019-03-13T15:10:56+00:00

The mutex for the regulator_dev must be controlled by the caller of
the regulator_notifier_call_chain(), as described in the comment
for that function.

Failure to mutex lock and unlock surrounding the notifier call results
in a kernel WARN_ON_ONCE() which will dump a backtrace for the
regulator_notifier_call_chain() when that function call is first made.
The mutex can be controlled using the regulator_lock/unlock() API.

Fixes: e4ee831f949a ("regulator: Add WM831x DC-DC buck convertor support")
Suggested-by: Adam Thomson 
Signed-off-by: Steve Twiss 
Acked-by: Charles Keepax 
Signed-off-by: Mark Brown

regulator: wm831x-dcdc: Convert to use regulator_set/get_current_limit_regmap

2019-03-04T00:00:27+00:00

Use regulator_set/get_current_limit_regmap helpers to save some code.

Signed-off-by: Axel Lin 
Acked-by: Charles Keepax 
Signed-off-by: Mark Brown

Merge branch 'for-5.0' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator into regulator-5.1

2019-03-03T23:49:46+00:00

regulator: wm831x-dcdc: Fix list of wm831x_dcdc_ilim from mA to uA

2019-02-26T11:47:56+00:00

The wm831x_dcdc_ilim entries needs to be uA because it is used to compare
with min_uA and max_uA.
While at it also make the array const and change to use unsigned int.

Fixes: e4ee831f949a ("regulator: Add WM831x DC-DC buck convertor support")
Signed-off-by: Axel Lin 
Acked-by: Charles Keepax 
Signed-off-by: Mark Brown

regulator: wm831x-dcdc: Convert to use regulator_linear_range for wm831x_buckv

2019-01-22T17:26:24+00:00

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown