From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@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>,
jingyi.wang@oss.qualcomm.com, aiqun.yu@oss.qualcomm.com,
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
Subject: Re: [PATCH v2 4/6] clk: qcom: rpmh: Add support for Kaanapali rpmh clocks
Date: Mon, 17 Nov 2025 13:28:46 +0530 [thread overview]
Message-ID: <cdbfe200-314b-4185-bb58-d528ed317610@oss.qualcomm.com> (raw)
In-Reply-To: <2jfvrt4r7ddagh2ztbad7qnjpcvulcrtr3ekul6i26qg6zcd44@dxfhl3265okx>
On 11/14/2025 4:38 PM, Dmitry Baryshkov wrote:
> On Fri, Nov 14, 2025 at 02:13:49PM +0530, Taniya Das wrote:
>>
>>
>> On 11/11/2025 4:16 PM, Dmitry Baryshkov wrote:
>>> On Thu, Oct 30, 2025 at 04:39:07PM +0530, Taniya Das wrote:
>>>> Add the RPMH clocks present in Kaanapali SoC.
>>>>
>>>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>>>> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
>>>> ---
>>>> drivers/clk/qcom/clk-rpmh.c | 42 ++++++++++++++++++++++++++++++++++++++++++
>>>> 1 file changed, 42 insertions(+)
>>>>
>>>> diff --git a/drivers/clk/qcom/clk-rpmh.c b/drivers/clk/qcom/clk-rpmh.c
>>>> index 1a98b3a0c528c24b600326e6b951b2edb6dcadd7..fd0fe312a7f2830a27e6effc0c0bd905d9d5ebed 100644
>>>> --- a/drivers/clk/qcom/clk-rpmh.c
>>>> +++ b/drivers/clk/qcom/clk-rpmh.c
>>>> @@ -395,6 +395,19 @@ DEFINE_CLK_RPMH_VRM(clk4, _a, "C4A_E0", 1);
>>>> DEFINE_CLK_RPMH_VRM(clk5, _a, "C5A_E0", 1);
>>>> DEFINE_CLK_RPMH_VRM(clk8, _a, "C8A_E0", 1);
>>>>
>>>> +DEFINE_CLK_RPMH_VRM(ln_bb_clk1, _a2_e0, "C6A_E0", 2);
>>>> +DEFINE_CLK_RPMH_VRM(ln_bb_clk2, _a2_e0, "C7A_E0", 2);
>>>> +DEFINE_CLK_RPMH_VRM(ln_bb_clk3, _a2_e0, "C8A_E0", 2);
>>>> +
>>>> +DEFINE_CLK_RPMH_VRM(rf_clk1, _a_e0, "C1A_E0", 1);
>>>> +DEFINE_CLK_RPMH_VRM(rf_clk2, _a_e0, "C2A_E0", 1);
>>>
>>> What is the difference between these clocks and clk[3458] defined few
>>> lines above? Why are they named differently? If the other name is
>>> incorrect, please fix it.
>>>
>>
>> Dmitry, my intention was to make a clear distinction between the ‘rf’
>> clocks and the ‘ln’ clocks. Since there could be overlap in the
>> numbering, I added prefixes for clarity. I should have applied the same
>> approach to clk[3458] as well. I will add the fix-up for the same.
>
> Why do we need to distinguish between them here? The resources in CMD-DB
> don't have such a difference. You'll select whether the clock is RF or
> LN when describing the platform data.
>
It is more for readibility and maintain a direct mapping with the PMIC
clock grid. This way we can immediately identify the clock type without
cross-referencing desc as the clock mapping here would indicate the type
of clock. Yes, the CMD-DB name does not reflect anything with the names
here. Please do let me know your suggestion.
>>
>>>> +
>>>> +DEFINE_CLK_RPMH_VRM(rf_clk3, _a2_e0, "C3A_E0", 2);
>>>> +DEFINE_CLK_RPMH_VRM(rf_clk4, _a2_e0, "C4A_E0", 2);
>>>> +DEFINE_CLK_RPMH_VRM(rf_clk5, _a2_e0, "C5A_E0", 2);
>>>> +
>>>> +DEFINE_CLK_RPMH_VRM(div_clk1, _a4_e0, "C11A_E0", 4);
>>>> +
>>>> DEFINE_CLK_RPMH_BCM(ce, "CE0");
>>>> DEFINE_CLK_RPMH_BCM(hwkm, "HK0");
>>>> DEFINE_CLK_RPMH_BCM(ipa, "IP0");
>>>> @@ -901,6 +914,34 @@ static const struct clk_rpmh_desc clk_rpmh_glymur = {
>>>> .num_clks = ARRAY_SIZE(glymur_rpmh_clocks),
>>>> };
>>>>
>>>> +static struct clk_hw *kaanapali_rpmh_clocks[] = {
>>>> + [RPMH_CXO_CLK] = &clk_rpmh_bi_tcxo_div2.hw,
>>>> + [RPMH_CXO_CLK_A] = &clk_rpmh_bi_tcxo_div2_ao.hw,
>>>> + [RPMH_DIV_CLK1] = &clk_rpmh_div_clk1_a4_e0.hw,
>>>> + [RPMH_LN_BB_CLK1] = &clk_rpmh_ln_bb_clk1_a2_e0.hw,
>>>> + [RPMH_LN_BB_CLK1_A] = &clk_rpmh_ln_bb_clk1_a2_e0_ao.hw,
>>>> + [RPMH_LN_BB_CLK2] = &clk_rpmh_ln_bb_clk2_a2_e0.hw,
>>>> + [RPMH_LN_BB_CLK2_A] = &clk_rpmh_ln_bb_clk2_a2_e0_ao.hw,
>>>> + [RPMH_LN_BB_CLK3] = &clk_rpmh_ln_bb_clk3_a2_e0.hw,
>>>> + [RPMH_LN_BB_CLK3_A] = &clk_rpmh_ln_bb_clk3_a2_e0_ao.hw,
>>>> + [RPMH_RF_CLK1] = &clk_rpmh_rf_clk1_a_e0.hw,
>>>> + [RPMH_RF_CLK1_A] = &clk_rpmh_rf_clk1_a_e0_ao.hw,
>>>> + [RPMH_RF_CLK2] = &clk_rpmh_rf_clk2_a_e0.hw,
>>>> + [RPMH_RF_CLK2_A] = &clk_rpmh_rf_clk2_a_e0_ao.hw,
>>>> + [RPMH_RF_CLK3] = &clk_rpmh_rf_clk3_a2_e0.hw,
>>>> + [RPMH_RF_CLK3_A] = &clk_rpmh_rf_clk3_a2_e0_ao.hw,
>>>> + [RPMH_RF_CLK4] = &clk_rpmh_rf_clk4_a2_e0.hw,
>>>> + [RPMH_RF_CLK4] = &clk_rpmh_rf_clk4_a2_e0_ao.hw,
>>>> + [RPMH_RF_CLK5_A] = &clk_rpmh_rf_clk5_a2_e0.hw,
>>>> + [RPMH_RF_CLK5_A] = &clk_rpmh_rf_clk5_a2_e0_ao.hw,
>>>> + [RPMH_IPA_CLK] = &clk_rpmh_ipa.hw,
>>>> +};
>>>> +
>>>> +static const struct clk_rpmh_desc clk_rpmh_kaanapali = {
>>>> + .clks = kaanapali_rpmh_clocks,
>>>> + .num_clks = ARRAY_SIZE(kaanapali_rpmh_clocks),
>>>> +};
>>>> +
>>>> static struct clk_hw *of_clk_rpmh_hw_get(struct of_phandle_args *clkspec,
>>>> void *data)
>>>> {
>>>> @@ -991,6 +1032,7 @@ static int clk_rpmh_probe(struct platform_device *pdev)
>>>>
>>>> static const struct of_device_id clk_rpmh_match_table[] = {
>>>> { .compatible = "qcom,glymur-rpmh-clk", .data = &clk_rpmh_glymur},
>>>> + { .compatible = "qcom,kaanapali-rpmh-clk", .data = &clk_rpmh_kaanapali},
>>>> { .compatible = "qcom,milos-rpmh-clk", .data = &clk_rpmh_milos},
>>>> { .compatible = "qcom,qcs615-rpmh-clk", .data = &clk_rpmh_qcs615},
>>>> { .compatible = "qcom,qdu1000-rpmh-clk", .data = &clk_rpmh_qdu1000},
>>>>
>>>> --
>>>> 2.34.1
>>>>
>>>
>>
>> --
>> Thanks,
>> Taniya Das
>>
>
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2025-11-17 7:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 11:09 [PATCH v2 0/6] Add support for Clock controllers for Kaanapali Taniya Das
2025-10-30 11:09 ` [PATCH v2 1/6] dt-bindings: clock: qcom-rpmhcc: Add RPMHCC " Taniya Das
2025-10-30 11:09 ` [PATCH v2 2/6] dt-bindings: clock: qcom: Document the Kaanapali TCSR Clock Controller Taniya Das
2025-10-30 11:09 ` [PATCH v2 3/6] dt-bindings: clock: qcom: Add Kaanapali Global clock controller Taniya Das
2025-10-30 11:09 ` [PATCH v2 4/6] clk: qcom: rpmh: Add support for Kaanapali rpmh clocks Taniya Das
2025-11-11 10:30 ` Jagadeesh Kona
2025-11-11 10:46 ` Dmitry Baryshkov
2025-11-11 11:44 ` Aiqun(Maria) Yu
2025-11-11 12:16 ` Dmitry Baryshkov
2025-11-12 9:21 ` Konrad Dybcio
2025-11-14 8:43 ` Taniya Das
2025-11-14 11:08 ` Dmitry Baryshkov
2025-11-17 7:58 ` Taniya Das [this message]
2025-11-18 4:34 ` Dmitry Baryshkov
2025-11-18 4:48 ` Taniya Das
2025-11-19 8:08 ` Dmitry Baryshkov
2025-10-30 11:09 ` [PATCH v2 5/6] clk: qcom: Add TCSR clock driver for Kaanapali Taniya Das
2025-11-04 3:35 ` Aiqun(Maria) Yu
2025-11-11 10:47 ` Dmitry Baryshkov
2025-11-18 6:44 ` Jingyi Wang
2025-11-21 17:26 ` Taniya Das
2025-10-30 11:09 ` [PATCH v2 6/6] clk: qcom: Add support for Global clock controller on Kaanapali Taniya Das
2025-11-03 13:32 ` Konrad Dybcio
2025-11-11 10:48 ` Dmitry Baryshkov
2025-11-21 17:24 ` Taniya Das
2025-11-04 1:58 ` (subset) [PATCH v2 0/6] Add support for Clock controllers for Kaanapali Bjorn Andersson
2025-11-11 10:44 ` Dmitry Baryshkov
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=cdbfe200-314b-4185-bb58-d528ed317610@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.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=jingyi.wang@oss.qualcomm.com \
--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 \
/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