From: Esteban Urrutia <[email protected]>

While using an OLE PLL type is correct according to downstream code, this
results in the display flickering at boot for SM8475 because downstream
uses EVO type configurations for both clocks, while, for some reason,
upstream uses EVO type configurations for SM8450 and OLE type
configurations for SM8475.
So far, no regressions have been observed and the display no longer
flickers.

Fixes: 7c0e8764dc33 ("clk: qcom: dispcc-sm8450: Add SM8475 support")
Signed-off-by: Esteban Urrutia <[email protected]>
---
 drivers/clk/qcom/dispcc-sm8450.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/clk/qcom/dispcc-sm8450.c b/drivers/clk/qcom/dispcc-sm8450.c
index 07f22b5b5ee5..2c0edc23eeb1 100644
--- a/drivers/clk/qcom/dispcc-sm8450.c
+++ b/drivers/clk/qcom/dispcc-sm8450.c
@@ -1833,11 +1833,9 @@ static int disp_cc_sm8450_probe(struct platform_device 
*pdev)
 
        if (of_device_is_compatible(pdev->dev.of_node, "qcom,sm8475-dispcc")) {
                /* Update DISPCC PLL0 */
-               disp_cc_pll0.regs = 
clk_alpha_pll_regs[CLK_ALPHA_PLL_TYPE_LUCID_OLE];
                disp_cc_pll0.clkr.hw.init = &sm8475_disp_cc_pll0_init;
 
                /* Update DISPCC PLL1 */
-               disp_cc_pll1.regs = 
clk_alpha_pll_regs[CLK_ALPHA_PLL_TYPE_LUCID_OLE];
                disp_cc_pll1.clkr.hw.init = &sm8475_disp_cc_pll1_init;
 
                disp_cc_pll0.config = &sm8475_disp_cc_pll0_config;

-- 
2.55.0



Reply via email to