Re: [PATCH v2 3/3] clk: qcom: dispcc-sm8450: Keep pll types as is for SM8475
Konrad Dybcio <[email protected]> Mon, 13 Jul 2026 12:57:30 +0200
| Newsgroups | org.kernel.vger.phone-devel,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-clk,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 7/12/26 5:10 AM, Esteban Urrutia via B4 Relay wrote: > 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. No, these are two separate hardware designs and you can't mix the configuration like that just because it so happens to circumvent a bug. Taking a peek at clk_lucid_evo_pll_configure, there's an early bailout: if (trion_pll_is_enabled(pll, regmap)) { pr_debug("Lucid Evo PLL is already enabled, skipping configuration\n"); return; } I think it should be fine to copy-paste it as-is for LUCID_OLE. Please check if that resolves your issue. Konrad