From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 08/11] clk: qcom: dispcc: Add support for display clock controller Kaanapali
Date: Mon, 1 Dec 2025 14:20:44 +0100 [thread overview]
Message-ID: <8d0ec7fc-6eb0-4b71-8e0f-3deaf1f489d6@oss.qualcomm.com> (raw)
In-Reply-To: <w3ezxipjucswfswfg2z7b7uyu55bssqatdnbxa6jflii4j7nym@lxsnidrewepu>
On 11/26/25 1:09 AM, Dmitry Baryshkov wrote:
> On Tue, Nov 25, 2025 at 11:15:17PM +0530, Taniya Das wrote:
>> Support the clock controller driver for Kaanapali to enable display SW to
>> be able to control the clocks.
>>
>> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
>> ---
[...]
>> +/* 257.142858 MHz Configuration */
>
> This is a bit strange frequency for the boot config.
The frequency map lists this odd cookie as the lowest predefined config,
perhaps it was pulled from there.
More interestingly, the only consumer of this PLL (MDP_CLK_SRC) makes no
effort to use the m/n/d registers, instead relying on the PLL to re-clock
for its ratesetting with a fixed divider of 3 (and div1 @ XO rate).
257.142858 * 3 = 771.428574 over-drives MDP_CLK_SRC, FWIW.
Taniya, we've seen something like this in camera too. Is there a reason
the frequency is being set this way?
Konrad
>
>> +static const struct alpha_pll_config disp_cc_pll0_config = {
>> + .l = 0xd,
>> + .cal_l = 0x48,
>> + .alpha = 0x6492,
>> + .config_ctl_val = 0x25c400e7,
>> + .config_ctl_hi_val = 0x0a8062e0,
>> + .config_ctl_hi1_val = 0xf51dea20,
>> + .user_ctl_val = 0x00000008,
>> + .user_ctl_hi_val = 0x00000002,
>> +};
>> +
>
next prev parent reply other threads:[~2025-12-01 13:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 17:45 [PATCH v2 00/11] Add support for Multimedia Clock controllers for Kaanapali Taniya Das
2025-11-25 17:45 ` [PATCH v2 01/11] clk: qcom: clk-alpha-pll: Update the PLL support for cal_l Taniya Das
2025-11-25 17:45 ` [PATCH v2 02/11] clk: qcom: clk-alpha-pll: Add support for controlling Pongo EKO_T PLL Taniya Das
2025-11-25 17:45 ` [PATCH v2 03/11] clk: qcom: clk-alpha-pll: Add support for controlling Rivian PLL Taniya Das
2025-11-25 17:45 ` [PATCH v2 04/11] dt-bindings: clock: qcom: document Kaanapali DISPCC clock controller Taniya Das
2025-11-25 17:45 ` [PATCH v2 05/11] dt-bindings: clock: qcom: Add support for CAMCC for Kaanapali Taniya Das
2025-11-26 9:26 ` Krzysztof Kozlowski
2025-12-16 10:47 ` Vladimir Zapolskiy
2025-11-25 17:45 ` [PATCH v2 06/11] dt-bindings: clock: qcom: Add Kaanapali video clock controller Taniya Das
2025-11-25 17:45 ` [PATCH v2 07/11] dt-bindings: clock: qcom: document the Kaanapali GPU Clock Controller Taniya Das
2025-11-26 9:35 ` Krzysztof Kozlowski
2025-12-04 6:49 ` Taniya Das
2025-12-16 8:51 ` Krzysztof Kozlowski
2025-12-17 9:32 ` Taniya Das
2025-12-17 10:09 ` Krzysztof Kozlowski
2025-12-17 13:21 ` Konrad Dybcio
2025-12-17 13:54 ` Krzysztof Kozlowski
2025-12-19 10:39 ` Taniya Das
2025-12-19 12:56 ` Krzysztof Kozlowski
2025-12-19 13:02 ` Konrad Dybcio
2025-12-19 14:45 ` Krzysztof Kozlowski
2025-12-23 10:49 ` Taniya Das
2025-11-25 17:45 ` [PATCH v2 08/11] clk: qcom: dispcc: Add support for display clock controller Kaanapali Taniya Das
2025-11-26 0:09 ` Dmitry Baryshkov
2025-12-01 13:20 ` Konrad Dybcio [this message]
2025-12-04 7:14 ` Taniya Das
2025-12-04 9:34 ` Konrad Dybcio
2025-12-19 13:24 ` Konrad Dybcio
2025-11-25 17:45 ` [PATCH v2 09/11] clk: qcom: camcc: Add support for camera clock controller for Kaanapali Taniya Das
2025-11-25 17:45 ` [PATCH v2 10/11] clk: qcom: Add support for VideoCC driver " Taniya Das
2025-12-01 13:15 ` Konrad Dybcio
2025-12-04 6:51 ` Taniya Das
2025-11-25 17:45 ` [PATCH v2 11/11] clk: qcom: Add support for GPUCC and GXCLK " Taniya Das
2025-12-17 13:22 ` 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=8d0ec7fc-6eb0-4b71-8e0f-3deaf1f489d6@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
--cc=vladimir.zapolskiy@linaro.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