diff options
| author | Melody Olvera <quic_molvera@quicinc.com> | 2024-11-11 16:26:45 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-12-14 20:04:07 +0100 |
| commit | 4bbdddcefeb595f41e5f5489663a6ae40b77f2a7 (patch) | |
| tree | 7e5119e8ec350a6c118007d77449521d6af3bee6 /include | |
| parent | db7fc56646cafe39599a4c21f1398e2bdfd5c185 (diff) | |
| download | linux-4bbdddcefeb595f41e5f5489663a6ae40b77f2a7.tar.gz linux-4bbdddcefeb595f41e5f5489663a6ae40b77f2a7.tar.bz2 linux-4bbdddcefeb595f41e5f5489663a6ae40b77f2a7.zip | |
regulator: qcom-rpmh: Update ranges for FTSMPS525
[ Upstream commit eeecf953d697cb7f0d916f9908a2b9f451bb2667 ]
All FTSMPS525 regulators support LV and MV ranges; however,
the boot loader firmware will determine which range to use as
the device boots.
Nonetheless, the driver cannot determine which range was selected,
so hardcoding the ranges as either LV or MV will not cover all cases
as it's possible for the firmware to select a range not supported by
the driver's current hardcoded values.
To this end, combine the ranges for the FTSMPS525s into one struct
and point all regulators to the updated combined struct. This should
work on all boards regardless of which range is selected by the firmware
and more accurately caputres the capability of this regulator on a
hardware level.
Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Link: https://patch.msgid.link/20241112002645.2803506-1-quic_molvera@quicinc.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions