From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Ajit Pandey <quic_ajipan@quicinc.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Taniya Das <quic_tdas@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
stable@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH V4 1/8] clk: qcom: clk-alpha-pll: Fix CAL_L_VAL override for LUCID EVO PLL
Date: Thu, 13 Jun 2024 11:19:34 +0300 [thread overview]
Message-ID: <68a18159-11ff-412c-b742-34ceb0f3a028@linaro.org> (raw)
In-Reply-To: <20240611133752.2192401-2-quic_ajipan@quicinc.com>
Hi Ajit,
On 6/11/24 16:37, Ajit Pandey wrote:
> In LUCID EVO PLL CAL_L_VAL and L_VAL bitfields are part of single
> PLL_L_VAL register. Update for L_VAL bitfield values in PLL_L_VAL
> register using regmap_write() API in __alpha_pll_trion_set_rate
> callback will override LUCID EVO PLL initial configuration related
> to PLL_CAL_L_VAL bit fields in PLL_L_VAL register.
>
> Observed random PLL lock failures during PLL enable due to such
> override in PLL calibration value. Use regmap_update_bits() with
> L_VAL bitfield mask instead of regmap_write() API to update only
> PLL_L_VAL bitfields in __alpha_pll_trion_set_rate callback.
>
> Fixes: 260e36606a03 ("clk: qcom: clk-alpha-pll: add Lucid EVO PLL configuration interfaces")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ajit Pandey <quic_ajipan@quicinc.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
thank you for the fix!
Acked-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2024-06-13 8:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:37 [PATCH V4 0/8] clk: qcom: Add support for DISPCC, CAMCC and GPUCC on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 1/8] clk: qcom: clk-alpha-pll: Fix CAL_L_VAL override for LUCID EVO PLL Ajit Pandey
2024-06-13 8:19 ` Vladimir Zapolskiy [this message]
2024-06-13 16:58 ` Konrad Dybcio
2024-06-11 13:37 ` [PATCH V4 2/8] dt-bindings: clock: qcom: add DISPCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 3/8] clk: qcom: Add DISPCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 4/8] dt-bindings: clock: qcom: add CAMCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 5/8] clk: qcom: Add CAMCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 6/8] dt-bindings: clock: qcom: add GPUCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 7/8] clk: qcom: Add GPUCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 8/8] arm64: dts: qcom: sm4450: add camera, display and gpu clock controller Ajit Pandey
2024-06-11 15:47 ` Dmitry Baryshkov
2024-06-13 7:41 ` Konrad Dybcio
2024-07-03 9:16 ` Ajit Pandey
2024-07-11 9:55 ` Konrad Dybcio
2024-07-12 9:53 ` Ajit Pandey
2024-07-12 12:22 ` Konrad Dybcio
2024-07-12 12:31 ` Ajit Pandey
2024-07-12 12:40 ` Konrad Dybcio
2024-07-16 8:39 ` Taniya Das
2024-07-16 10:39 ` Konrad Dybcio
2024-07-26 8:18 ` Ajit Pandey
2024-08-15 20:40 ` (subset) [PATCH V4 0/8] clk: qcom: Add support for DISPCC, CAMCC and GPUCC on SM4450 Bjorn Andersson
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=68a18159-11ff-412c-b742-34ceb0f3a028@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).