Although sc7180 is supposed to have a hardware fix that means that we
don't have to restore the DLL config like we did with sdm845,
apparently the hardware fix doesn't work in all cases. Until it's
understood under exactly which cases we the hardware fix malfunctions,
let's go back to restoring the DLL config whenever we do runtime
resume. This is safe and gets things working again.
NOTE: we don't need to introduce a whole new "struct
sdhci_msm_variant_info" for sc7180 since it would be exactly the same
as the sdm845 one. We'll just refer to that one.
Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
---
drivers/mmc/host/sdhci-msm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
index b7e47107a31a..a88db3f376bd 100644
--- a/drivers/mmc/host/sdhci-msm.c
+++ b/drivers/mmc/host/sdhci-msm.c
@@ -2148,6 +2148,7 @@ static const struct sdhci_msm_variant_info sm8250_sdhci_var = {
static const struct of_device_id sdhci_msm_dt_match[] = {
{.compatible = "qcom,sdhci-msm-v4", .data = &sdhci_msm_mci_var},
{.compatible = "qcom,sdhci-msm-v5", .data = &sdhci_msm_v5_var},
+ {.compatible = "qcom,sc7180-sdhci", .data = &sdm845_sdhci_var},
{.compatible = "qcom,sdm845-sdhci", .data = &sdm845_sdhci_var},
{.compatible = "qcom,sm8250-sdhci", .data = &sm8250_sdhci_var},
{},
--
2.28.0.297.g1956fa8f8d-goog
