From: Melody Olvera <quic_molvera@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
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>,
Taniya Das <quic_tdas@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH v2 2/7] clk: qcom: rpmh: Add support for SM8750 rpmh clocks
Date: Mon, 18 Nov 2024 10:53:16 -0800 [thread overview]
Message-ID: <8d3c2efd-b6c3-4b01-ae01-78460f4e9f26@quicinc.com> (raw)
In-Reply-To: <5pgwerxhqhyr2u47grqzgzvvng4rojzq4gozil7vy37bew5pqj@wt676vfjs7bg>
On 11/15/2024 7:31 AM, Dmitry Baryshkov wrote:
> On Mon, Nov 11, 2024 at 04:28:02PM -0800, Melody Olvera wrote:
>> From: Taniya Das <quic_tdas@quicinc.com>
>>
>> Add the RPMH clocks present in SM8750 SoC and fix the match table to
>> sort it alphabetically.
>>
>> Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
>> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
>> ---
>> drivers/clk/qcom/clk-rpmh.c | 28 +++++++++++++++++++++++++++-
>> 1 file changed, 27 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/qcom/clk-rpmh.c b/drivers/clk/qcom/clk-rpmh.c
>> index eefc322ce367..a3b381e34e48 100644
>> --- a/drivers/clk/qcom/clk-rpmh.c
>> +++ b/drivers/clk/qcom/clk-rpmh.c
>> @@ -368,6 +368,10 @@ DEFINE_CLK_RPMH_VRM(rf_clk2, _d, "rfclkd2", 1);
>> DEFINE_CLK_RPMH_VRM(rf_clk3, _d, "rfclkd3", 1);
>> DEFINE_CLK_RPMH_VRM(rf_clk4, _d, "rfclkd4", 1);
>>
>> +DEFINE_CLK_RPMH_VRM(rf_clk3, _a2, "rfclka3", 2);
>> +DEFINE_CLK_RPMH_VRM(rf_clk4, _a2, "rfclka4", 2);
>> +DEFINE_CLK_RPMH_VRM(rf_clk5, _a2, "rfclka5", 2);
> Are the two last clocks defined "for the future platforms"?
I'm unsure; I'll let Taniya comment.
>
>> +
>> DEFINE_CLK_RPMH_VRM(clk1, _a1, "clka1", 1);
>> DEFINE_CLK_RPMH_VRM(clk2, _a1, "clka2", 1);
>> DEFINE_CLK_RPMH_VRM(clk3, _a1, "clka3", 1);
>> @@ -807,6 +811,27 @@ static const struct clk_rpmh_desc clk_rpmh_x1e80100 = {
>> .num_clks = ARRAY_SIZE(x1e80100_rpmh_clocks),
>> };
>>
>> +static struct clk_hw *sm8750_rpmh_clocks[] = {
>> + [RPMH_CXO_CLK] = &clk_rpmh_bi_tcxo_div2.hw,
>> + [RPMH_CXO_CLK_A] = &clk_rpmh_bi_tcxo_div2_ao.hw,
>> + [RPMH_LN_BB_CLK1] = &clk_rpmh_clk6_a2.hw,
>> + [RPMH_LN_BB_CLK1_A] = &clk_rpmh_clk6_a2_ao.hw,
>> + [RPMH_LN_BB_CLK3] = &clk_rpmh_clk8_a2.hw,
>> + [RPMH_LN_BB_CLK3_A] = &clk_rpmh_clk8_a2_ao.hw,
>> + [RPMH_RF_CLK1] = &clk_rpmh_rf_clk1_a.hw,
>> + [RPMH_RF_CLK1_A] = &clk_rpmh_rf_clk1_a_ao.hw,
>> + [RPMH_RF_CLK2] = &clk_rpmh_rf_clk2_a.hw,
>> + [RPMH_RF_CLK2_A] = &clk_rpmh_rf_clk2_a_ao.hw,
>> + [RPMH_RF_CLK3] = &clk_rpmh_rf_clk3_a2.hw,
>> + [RPMH_RF_CLK3_A] = &clk_rpmh_rf_clk3_a2_ao.hw,
>> + [RPMH_IPA_CLK] = &clk_rpmh_ipa.hw,
>> +};
>> +
>> +static const struct clk_rpmh_desc clk_rpmh_sm8750 = {
>> + .clks = sm8750_rpmh_clocks,
>> + .num_clks = ARRAY_SIZE(sm8750_rpmh_clocks),
>> +};
>> +
>> static struct clk_hw *of_clk_rpmh_hw_get(struct of_phandle_args *clkspec,
>> void *data)
>> {
>> @@ -894,6 +919,7 @@ static const struct of_device_id clk_rpmh_match_table[] = {
>> { .compatible = "qcom,sa8775p-rpmh-clk", .data = &clk_rpmh_sa8775p},
>> { .compatible = "qcom,sar2130p-rpmh-clk", .data = &clk_rpmh_sar2130p},
>> { .compatible = "qcom,sc7180-rpmh-clk", .data = &clk_rpmh_sc7180},
>> + { .compatible = "qcom,sc7280-rpmh-clk", .data = &clk_rpmh_sc7280},
>> { .compatible = "qcom,sc8180x-rpmh-clk", .data = &clk_rpmh_sc8180x},
>> { .compatible = "qcom,sc8280xp-rpmh-clk", .data = &clk_rpmh_sc8280xp},
>> { .compatible = "qcom,sdm845-rpmh-clk", .data = &clk_rpmh_sdm845},
>> @@ -909,7 +935,7 @@ static const struct of_device_id clk_rpmh_match_table[] = {
>> { .compatible = "qcom,sm8450-rpmh-clk", .data = &clk_rpmh_sm8450},
>> { .compatible = "qcom,sm8550-rpmh-clk", .data = &clk_rpmh_sm8550},
>> { .compatible = "qcom,sm8650-rpmh-clk", .data = &clk_rpmh_sm8650},
>> - { .compatible = "qcom,sc7280-rpmh-clk", .data = &clk_rpmh_sc7280},
> Please don't mix fixes and actual code. I'd suggest splitting sc7280
> move to the separate commit.
Bryan O'Donoghue requested we sort these as part of this patch. I don't
feel strongly either way,
but clear guidance here would be appreciated.
Thanks,
Melody
>
>> + { .compatible = "qcom,sm8750-rpmh-clk", .data = &clk_rpmh_sm8750},
>> { .compatible = "qcom,x1e80100-rpmh-clk", .data = &clk_rpmh_x1e80100},
>> { }
>> };
>> --
>> 2.46.1
>>
next prev parent reply other threads:[~2024-11-18 18:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 0:28 [PATCH v2 0/7] clks: qcom: Introduce clks for SM8750 Melody Olvera
2024-11-12 0:28 ` [PATCH v2 1/7] dt-bindings: clock: qcom-rpmhcc: Add RPMHCC " Melody Olvera
2024-11-20 8:15 ` Krzysztof Kozlowski
2024-11-12 0:28 ` [PATCH v2 2/7] clk: qcom: rpmh: Add support for SM8750 rpmh clocks Melody Olvera
2024-11-15 15:31 ` Dmitry Baryshkov
2024-11-18 18:53 ` Melody Olvera [this message]
2024-11-19 1:58 ` Dmitry Baryshkov
2024-12-04 4:42 ` Taniya Das
2024-12-04 6:21 ` Taniya Das
2024-11-12 0:28 ` [PATCH v2 3/7] clk: qcom: clk-alpha-pll: Add support for controlling Taycan PLLs Melody Olvera
2024-11-15 15:32 ` Dmitry Baryshkov
2024-11-12 0:28 ` [PATCH v2 4/7] dt-bindings: clock: qcom: Add SM8750 GCC Melody Olvera
2024-11-20 8:17 ` Krzysztof Kozlowski
2024-11-25 21:15 ` Melody Olvera
2024-12-04 7:17 ` Taniya Das
2024-12-04 9:24 ` Taniya Das
2024-11-12 0:28 ` [PATCH v2 5/7] clk: qcom: Add support for GCC clock controller on SM8750 Melody Olvera
2024-11-15 15:34 ` Dmitry Baryshkov
2024-11-18 19:30 ` Melody Olvera
2024-11-19 1:59 ` Dmitry Baryshkov
2024-11-25 21:31 ` Melody Olvera
2024-11-26 7:37 ` Dmitry Baryshkov
2024-11-12 0:28 ` [PATCH v2 6/7] dt-bindings: clock: qcom: Document the SM8750 TCSR Clock Controller Melody Olvera
2024-11-12 0:28 ` [PATCH v2 7/7] clk: qcom: Add TCSR clock driver for SM8750 Melody Olvera
2024-11-15 15:37 ` 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=8d3c2efd-b6c3-4b01-ae01-78460f4e9f26@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_satyap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=quic_tsoni@quicinc.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