From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
andersson@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
konradybcio@kernel.org, rafael@kernel.org,
viresh.kumar@linaro.org, ilia.lin@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/4] clk: qcom: apss-ipq5424: Add ipq5424 apss clock controller
Date: Sat, 1 Feb 2025 16:25:47 +0100 [thread overview]
Message-ID: <6c8bb178-1758-4b73-bbaf-8572dc1216d3@oss.qualcomm.com> (raw)
In-Reply-To: <123a324c-561a-4081-be43-8d8ed0662acc@quicinc.com>
On 30.01.2025 11:03 AM, Sricharan Ramabadhran wrote:
>
>
> On 1/28/2025 5:29 PM, Konrad Dybcio wrote:
>> On 27.01.2025 10:31 AM, Sricharan R wrote:
>>> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>>>
>>> CPU on Qualcomm ipq5424 is clocked by huayra PLL with RCG support.
>>> Add support for the APSS PLL, RCG and clock enable for ipq5424.
>>> The PLL, RCG register space are clubbed. Hence adding new APSS driver
>>> for both PLL and RCG/CBC control. Also the L3 cache has a separate pll
>>> and needs to be scaled along with the CPU.
>>>
>>> Co-developed-by: Md Sadre Alam <quic_mdalam@quicinc.com>
>>> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
>>> Signed-off-by: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>>> ---
[...]
>>> + clk_alpha_pll_configure(&ipq5424_l3_pll, regmap, &l3_pll_config);
>>> +
>>> + clk_alpha_pll_configure(&ipq5424_apss_pll, regmap, &apss_pll_config);
>>> +
>>> + ret = qcom_cc_really_probe(dev, &apss_ipq5424_desc, regmap);
>>> + if (ret)
>>> + return ret;
>>> +
>>> + dev_dbg(&pdev->dev, "Registered APSS & L3 clock provider\n");
>>> +
>>> + apss_ipq5424_cfg->dev = dev;
>>> + apss_ipq5424_cfg->hw = &apss_silver_clk_src.clkr.hw;
>>> + apss_ipq5424_cfg->cpu_clk_notifier.notifier_call = cpu_clk_notifier_fn;
>>> +
>>> + apss_ipq5424_cfg->l3_clk = clk_hw_get_clk(&l3_core_clk.clkr.hw, "l3_clk");
>>> + if (IS_ERR(apss_ipq5424_cfg->l3_clk)) {
>>> + dev_err(&pdev->dev, "Failed to get L3 clk, %ld\n",
>>> + PTR_ERR(apss_ipq5424_cfg->l3_clk));
>>> + return PTR_ERR(apss_ipq5424_cfg->l3_clk);
>>> + }
>>
>> Now that you'll use OPP, you can drop all this getting.. maybe even the
>> apss_ipq5424_cfg struct could be let go
>
> ok, is the suggestion here to use devm_pm_opp_set_config ?
Since what you tried to do here is binding CPU and L3 frequencies together,
yeah, we can just scale two clocks from OPP.
On some newer platforms using the epss-l3 driver, or on msm8996 with a more
complex setup, we expose the L3 voter as an interconnect, but here it would
seem that we directly control the clock that feeds it.
Konrad
next prev parent reply other threads:[~2025-02-01 15:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 9:31 [PATCH 0/4] Enable cpufreq for IPQ5424 Sricharan R
2025-01-27 9:31 ` [PATCH 1/4] dt-bindings: clock: ipq5424-apss-clk: Add ipq5424 apss clock controller Sricharan R
2025-01-28 7:34 ` Krzysztof Kozlowski
2025-01-28 11:15 ` Sricharan Ramabadhran
2025-01-28 12:30 ` Krzysztof Kozlowski
2025-01-30 10:39 ` Sricharan Ramabadhran
2025-02-01 15:21 ` Konrad Dybcio
2025-02-02 14:38 ` Krzysztof Kozlowski
2025-01-27 9:31 ` [PATCH 2/4] clk: qcom: apss-ipq5424: " Sricharan R
2025-01-28 7:48 ` Varadarajan Narayanan
2025-01-29 11:39 ` Sricharan Ramabadhran
2025-01-28 11:59 ` Konrad Dybcio
2025-01-30 10:03 ` Sricharan Ramabadhran
2025-02-01 15:25 ` Konrad Dybcio [this message]
2025-02-04 6:28 ` Sricharan Ramabadhran
2025-02-10 19:14 ` Konrad Dybcio
2025-01-27 9:31 ` [PATCH 3/4] cpufreq: qcom-nvmem: Enable cpufreq for ipq5424 Sricharan R
2025-01-27 15:12 ` Konrad Dybcio
2025-01-27 9:31 ` [PATCH 4/4] arm64: dts: qcom: ipq5424: Enable cpufreq support Sricharan R
2025-03-08 18:18 ` 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=6c8bb178-1758-4b73-bbaf-8572dc1216d3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--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=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_srichara@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@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