From: Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Ilia Lin <ilia.lin@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
Mukesh Ojha <quic_mojha@quicinc.com>
Subject: Re: [PATCH v2 0/3] Add support for the IPQ5321 SoC
Date: Mon, 27 May 2024 10:07:30 +0530 [thread overview]
Message-ID: <aeb32037-4e06-4b6a-8b4d-7b8ef0a0ad16@quicinc.com> (raw)
In-Reply-To: <12e5708a-ea6e-4798-a487-f2465c848278@quicinc.com>
On 4/6/2024 8:18 PM, Kathiravan Thirumoorthy wrote:
>
>
> On 3/25/2024 9:19 PM, Kathiravan Thirumoorthy wrote:
>> IPQ5321 SoC belong to IPQ5332 family. Add the SoC ID and the cpufreq
>> support. Maximum cpufreq for IPQ5321 is 1.1GHZ, which is determined
>> based on the eFuse.
>>
>> Viresh is okay to merge the cpufreq change via qcom tree[1] and provided
>> his Ack.
>>
>> [1]
>> https://lore.kernel.org/linux-arm-msm/20240306053200.6iwrviltwt3pnfnt@vireshk-i7/
>
>
> Gentle Reminder...
Bjorn,
Can this series picked up for v6.11?
I applied this series on top of qcom/for-next and it's applying cleanly.
Do let me know if I have to send V3 in any case.
Thanks,
Kathiravan.
>
>>
>> Signed-off-by: Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>
>> ---
>> Changes in v2:
>> - rebase on next-20240325
>> - pick up the tags
>> - Link to v1:
>>
>> https://lore.kernel.org/linux-arm-msm/20240228-ipq5321-sku-support-v1-0-14e4d4715f4b@quicinc.com/
>>
>> ---
>> Kathiravan Thirumoorthy (3):
>> dt-bindings: arm: qcom,ids: Add SoC ID for IPQ5321
>> soc: qcom: socinfo: Add SoC ID for IPQ5321
>> cpufreq: qcom-nvmem: add support for IPQ5321
>>
>> drivers/cpufreq/qcom-cpufreq-nvmem.c | 1 +
>> drivers/soc/qcom/socinfo.c | 1 +
>> include/dt-bindings/arm/qcom,ids.h | 1 +
>> 3 files changed, 3 insertions(+)
>> ---
>> base-commit: 1fdad13606e104ff103ca19d2d660830cb36d43e
>> change-id: 20240228-ipq5321-sku-support-bd07056d5e01
>>
>> Best regards,
next prev parent reply other threads:[~2024-05-27 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 15:49 Kathiravan Thirumoorthy
2024-03-25 15:49 ` [PATCH v2 1/3] dt-bindings: arm: qcom,ids: Add SoC ID for IPQ5321 Kathiravan Thirumoorthy
2024-03-25 15:49 ` [PATCH v2 2/3] soc: qcom: socinfo: " Kathiravan Thirumoorthy
2024-03-25 15:49 ` [PATCH v2 3/3] cpufreq: qcom-nvmem: add support " Kathiravan Thirumoorthy
2024-04-06 14:48 ` [PATCH v2 0/3] Add support for the IPQ5321 SoC Kathiravan Thirumoorthy
2024-05-27 4:37 ` Kathiravan Thirumoorthy [this message]
2024-05-28 3:32 ` 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=aeb32037-4e06-4b6a-8b4d-7b8ef0a0ad16@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®