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>,
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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: clk-rpmh: Update the clock suffix for Glymur
Date: Tue, 25 Nov 2025 23:58:35 +0530 [thread overview]
Message-ID: <81b6e9d2-209a-4f8d-8644-3a0dc77dd94d@oss.qualcomm.com> (raw)
In-Reply-To: <pkcwprrzpvbe6sxuuzanaqquhezz2ftoxtdt2fuufrjpmnyeqx@e3oodiuwhy4p>
On 11/25/2025 11:56 PM, Dmitry Baryshkov wrote:
> On Tue, Nov 25, 2025 at 11:42:39PM +0530, Taniya Das wrote:
>> Update the RPMh VRM clock definitions for Glymur to add the suffix to
>> indicate the clock div and e0 for the C3A_E0, C4A_E0, C5A_E0, and
>> C8A_E0 clock resources.
>>
>> Fixes: ebcb9db98bda ("clk: qcom: rpmh: Add support for Glymur rpmh clocks")
>
> It's not a bug, there is nothing to fix.
>
Will remove the fixes tag.
>> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
>> ---
>> drivers/clk/qcom/clk-rpmh.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/clk/qcom/clk-rpmh.c b/drivers/clk/qcom/clk-rpmh.c
>> index 1a98b3a0c528c24b600326e6b951b2edb6dcadd7..a370ab2d96c34fa8e7a090e8427b11008318c02f 100644
>> --- a/drivers/clk/qcom/clk-rpmh.c
>> +++ b/drivers/clk/qcom/clk-rpmh.c
>> @@ -390,10 +390,10 @@ DEFINE_CLK_RPMH_VRM(clk7, _a4, "clka7", 4);
>>
>> DEFINE_CLK_RPMH_VRM(div_clk1, _div2, "divclka1", 2);
>>
>> -DEFINE_CLK_RPMH_VRM(clk3, _a, "C3A_E0", 1);
>> -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(clk3, _a1_e0, "C3A_E0", 1);
>> +DEFINE_CLK_RPMH_VRM(clk4, _a1_e0, "C4A_E0", 1);
>> +DEFINE_CLK_RPMH_VRM(clk5, _a1_e0, "C5A_E0", 1);
>> +DEFINE_CLK_RPMH_VRM(clk8, _a1_e0, "C8A_E0", 1);
>>
>> DEFINE_CLK_RPMH_BCM(ce, "CE0");
>> DEFINE_CLK_RPMH_BCM(hwkm, "HK0");
>>
>> ---
>> base-commit: 92fd6e84175befa1775e5c0ab682938eca27c0b2
>> change-id: 20251125-glymur_rpmhcc_fix-5daa36a1e8ff
>>
>> Best regards,
>> --
>> Taniya Das <taniya.das@oss.qualcomm.com>
>>
>
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2025-11-25 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 18:12 [PATCH] clk: qcom: clk-rpmh: Update the clock suffix for Glymur Taniya Das
2025-11-25 18:26 ` Dmitry Baryshkov
2025-11-25 18:28 ` Taniya Das [this message]
2025-11-27 7:57 ` kernel test robot
2025-11-27 19:29 ` kernel test robot
2025-11-28 9:34 ` Taniya Das
2025-12-18 2:39 ` Bjorn Andersson
2025-12-18 2:41 ` Bjorn Andersson
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=81b6e9d2-209a-4f8d-8644-3a0dc77dd94d@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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