Devicetree
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Georgi Djakov <djakov@kernel.org>,
	Shawn Guo <shengchao.guo@oss.qualcomm.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Taniya Das <taniya.das@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 04/12] clk: qcom: gcc-mdm9607: Fix BIMC PLL definition
Date: Wed, 10 Jun 2026 15:56:08 +0200	[thread overview]
Message-ID: <ails-CZAOrq_wWBm@linaro.org> (raw)
In-Reply-To: <69cc948f-bb4f-49e7-b050-9e3805aef758@oss.qualcomm.com>

On Wed, Jun 10, 2026 at 03:46:00PM +0200, Konrad Dybcio wrote:
> On 6/9/26 4:14 PM, Stephan Gerhold wrote:
> > From: Stephan Gerhold <stephan@gerhold.net>
> > 
> > The gcc-mdm9607 driver was originally based on gcc-msm8916, but a closer
> > match nowadays is gcc-msm8909. Looking at the differences between
> > gcc-mdm9607 and gcc-msm8909, there is quite some confusion around the
> > definitions for the BIMC PLL.
> > 
> > It turns out the BIMC PLL on MDM9607 is actually an Alpha PLL just like on
> > MSM8909. We can vote for it using BIT(2), which explains why BIT(3) was
> > used for GPLL2.
> > 
> > Replace the definitions of the BIMC PLL in gcc-mdm9607 with the ones from
> > gcc-msm8909 to make sure we read the PLL status correctly and don't make
> > accidental incorrect changes to the PLL configuration. With this change,
> > the rate of the BIMC PLL (600.6 MHz) is displayed correctly in debugfs.
> > 
> > The clock naming typically used for Alpha PLLs differs from the older vote
> > PLLs. There is no device tree upstream for MDM9607 yet, so we can still
> > safely change the dt-bindings. Nevertheless, by keeping the old ID values
> > and swapping the two entries we can preserve ABI compatibility for compiled
> > DTBs. Previously, BIMC_PLL_VOTE (71) was the final PLL clock to reference
> > when needed, this is now just BIMC_PLL. The previous parent BIMC_PLL (70)
> > is now the parent BIMC_PLL_EARLY clock.
> > 
> > Cc: stable@vger.kernel.org
> > Fixes: 48b7253264ea ("clk: qcom: Add MDM9607 GCC driver")
> > Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> > ---
> 
> I think we may be better off removing the NoC PLLs and defer controlling
> them to RPM, on all platforms that define them..
> 

Well, this is not controlling them, it just allows reading them. And
that works pretty well, so I'm not sure why we would need to remove that
on platforms where it works?

Thanks,
Stephan

  reply	other threads:[~2026-06-10 13:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 14:14 [PATCH 00/12] clk: qcom: Assorted fixes for gcc-mdm9607 (and gcc-msm8916/39) Stephan Gerhold
2026-06-09 14:14 ` [PATCH 01/12] clk: qcom: gcc-msm8916: Fix enable_reg for gcc_blsp1_sleep_clk Stephan Gerhold
2026-06-10 13:40   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 02/12] clk: qcom: gcc-msm8939: " Stephan Gerhold
2026-06-10 13:40   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 03/12] clk: qcom: gcc-mdm9607: " Stephan Gerhold
2026-06-10 13:42   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 04/12] clk: qcom: gcc-mdm9607: Fix BIMC PLL definition Stephan Gerhold
2026-06-10 13:46   ` Konrad Dybcio
2026-06-10 13:56     ` Stephan Gerhold [this message]
2026-06-09 14:14 ` [PATCH 05/12] clk: qcom: gcc-mdm9607: Fix halt_reg for gcc_apss_axi_clk Stephan Gerhold
2026-06-10 13:43   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 06/12] clk: qcom: gcc-mdm9607: Increase delay for USB PHY reset Stephan Gerhold
2026-06-10 13:46   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 07/12] clk: qcom: gcc-mdm9607: Drop incorrect apss_tcu_clk_src Stephan Gerhold
2026-06-09 14:27   ` sashiko-bot
2026-06-10 13:50   ` Konrad Dybcio
2026-06-10 14:09     ` Stephan Gerhold
2026-06-09 14:14 ` [PATCH 08/12] clk: qcom: gcc-mdm9607: Drop incorrect system_noc_bfdcd_clk_src Stephan Gerhold
2026-06-10 13:50   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 09/12] dt-bindings: clock: qcom: gcc-mdm9607: Drop incorrect clocks Stephan Gerhold
2026-06-09 14:14 ` [PATCH 10/12] dt-bindings: clock: qcom,gcc-mdm9607: Add missing "clocks" property Stephan Gerhold
2026-06-10 13:44   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 11/12] dt-bindings: clock: qcom,gcc-mdm9607: Use proper address in example Stephan Gerhold
2026-06-10 13:44   ` Konrad Dybcio
2026-06-09 14:14 ` [PATCH 12/12] clk: qcom: gcc-mdm9607: Drop redundant register update during probe Stephan Gerhold
2026-06-10 13:44   ` Konrad Dybcio

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=ails-CZAOrq_wWBm@linaro.org \
    --to=stephan.gerhold@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.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=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shengchao.guo@oss.qualcomm.com \
    --cc=taniya.das@oss.qualcomm.com \
    /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