diff options
| author | Douglas Anderson <dianders@chromium.org> | 2023-03-24 16:34:06 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2023-03-24 17:20:05 +0300 |
| commit | ad44ac082fdff7ee57fe125432f7d9d7cb610a23 (patch) | |
| tree | 3f9d030c9c517f3bb3eb82acb83b068a6c133fb1 /drivers/regulator/qcom-rpmh-regulator.c | |
| parent | 58973046c1bf782cac01644a9dcd8e5bba9c2f16 (diff) | |
| download | linux-ad44ac082fdff7ee57fe125432f7d9d7cb610a23.tar.xz | |
regulator: qcom-rpmh: Revert "regulator: qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS"
This reverts commit 58973046c1bf ("regulator: qcom-rpmh: Use
PROBE_FORCE_SYNCHRONOUS"). Further digging into the problems that
prompted the us to switch to synchronous probe showed that the root
cause was a missing "rootwait" in the kernel command line
arguments. Let's reinstate asynchronous probe.
Fixes: 58973046c1bf ("regulator: qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS")
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20230324063357.1.Ifdf3625a3c5c9467bd87bfcdf726c884ad220a35@changeid
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/regulator/qcom-rpmh-regulator.c')
| -rw-r--r-- | drivers/regulator/qcom-rpmh-regulator.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/regulator/qcom-rpmh-regulator.c b/drivers/regulator/qcom-rpmh-regulator.c index 903032b2875f..4826d60e5d95 100644 --- a/drivers/regulator/qcom-rpmh-regulator.c +++ b/drivers/regulator/qcom-rpmh-regulator.c @@ -1462,7 +1462,7 @@ MODULE_DEVICE_TABLE(of, rpmh_regulator_match_table); static struct platform_driver rpmh_regulator_driver = { .driver = { .name = "qcom-rpmh-regulator", - .probe_type = PROBE_FORCE_SYNCHRONOUS, + .probe_type = PROBE_PREFER_ASYNCHRONOUS, .of_match_table = of_match_ptr(rpmh_regulator_match_table), }, .probe = rpmh_regulator_probe, |