From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: esteuwu@proton.me, Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Danila Tikhonov <danila@jiaxyga.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] clk: qcom: dispcc-sm8450: Keep pll types as is for SM8475
Date: Mon, 13 Jul 2026 12:57:30 +0200 [thread overview]
Message-ID: <d6a56ee7-2380-4e2a-b217-6d7398944279@oss.qualcomm.com> (raw)
In-Reply-To: <20260711-sm8450-qol-dispcc-v2-3-fc1a07ac5601@proton.me>
On 7/12/26 5:10 AM, Esteban Urrutia via B4 Relay wrote:
> From: Esteban Urrutia <esteuwu@proton.me>
>
> 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
next prev parent reply other threads:[~2026-07-13 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 3:10 [PATCH v2 0/3] SM8450 QoL changes (dispcc) Esteban Urrutia via B4 Relay
2026-07-12 3:10 ` [PATCH v2 1/3] clk: qcom: dispcc-sm8450: Fix disp_cc_mdss_mdp_clk_src ops Esteban Urrutia via B4 Relay
2026-07-13 10:50 ` Konrad Dybcio
2026-07-12 3:10 ` [PATCH v2 2/3] clk: qcom: dispcc-sm8450: Migrate to qcom_cc_driver_data Esteban Urrutia via B4 Relay
2026-07-13 10:47 ` Konrad Dybcio
2026-07-13 14:05 ` Esteban Urrutia
2026-07-12 3:10 ` [PATCH v2 3/3] clk: qcom: dispcc-sm8450: Keep pll types as is for SM8475 Esteban Urrutia via B4 Relay
2026-07-13 10:57 ` Konrad Dybcio [this message]
2026-07-13 22:47 ` Esteban Urrutia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6a56ee7-2380-4e2a-b217-6d7398944279@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=danila@jiaxyga.com \
--cc=esteuwu@proton.me \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®