diff options
| author | Vincent Whitchurch <vincent.whitchurch@axis.com> | 2020-09-02 15:09:52 +0200 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2020-09-02 20:13:29 +0200 |
| commit | 59ae97a7a9e1499c2070e29841d1c4be4ae2994a (patch) | |
| tree | d0bc3d5efcbc64bb4de8d96f021524da187e3eb4 /drivers/ide | |
| parent | regulator: core: Fix slab-out-of-bounds in regulator_unlock_recursive() (diff) | |
| download | linux-59ae97a7a9e1499c2070e29841d1c4be4ae2994a.tar.xz linux-59ae97a7a9e1499c2070e29841d1c4be4ae2994a.zip | |
regulator: pwm: Fix machine constraints application
If the zero duty cycle doesn't correspond to any voltage in the voltage
table, the PWM regulator returns an -EINVAL from get_voltage_sel() which
results in the core erroring out with a "failed to get the current
voltage" and ending up not applying the machine constraints.
Instead, return -ENOTRECOVERABLE which makes the core set the voltage
since it's at an unknown value.
For example, with this device tree:
fooregulator {
compatible = "pwm-regulator";
pwms = <&foopwm 0 100000>;
regulator-min-microvolt = <2250000>;
regulator-max-microvolt = <2250000>;
regulator-name = "fooregulator";
regulator-always-on;
regulator-boot-on;
voltage-table = <2250000 30>;
};
Before this patch:
fooregulator: failed to get the current voltage(-22)
After this patch:
fooregulator: Setting 2250000-2250000uV
fooregulator: 2250 mV
Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
Link: https://lore.kernel.org/r/20200902130952.24880-1-vincent.whitchurch@axis.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/ide')
0 files changed, 0 insertions, 0 deletions