From: Viresh Kumar <viresh.kumar@linaro.org>
To: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ilia Lin <ilia.lin@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 3/3] cpufreq: qcom-nvmem: add support for QCF3211 & IPQ5211
Date: Thu, 1 Oct 2026 11:52:03 +0530 [thread overview]
Message-ID: <ar38C5omDdaXQAID@vireshk-B250M-D3H> (raw)
In-Reply-To: <20260922-ipq52xx_new_ids-v2-3-4b1a0f3d04b2@oss.qualcomm.com>
On 22-09-26, 10:03, Kathiravan Thirumoorthy wrote:
> Like all other SoCs in IPQ5210 family, cpufreq for QCF3211 & IPQ5211 is
> also determined by the eFuse. Add support for the same.
>
> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
> ---
> drivers/cpufreq/qcom-cpufreq-nvmem.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
> index efa766e98d86..9f2e6e6c0905 100644
> --- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
> +++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
> @@ -205,6 +205,8 @@ static int qcom_cpufreq_kryo_name_version(struct device *cpu_dev,
> case QCOM_ID_QCF2200:
> case QCOM_ID_QCF3200:
> case QCOM_ID_QCF3210:
> + case QCOM_ID_QCF3211:
> + case QCOM_ID_IPQ5211:
> drv->versions = (*speedbin == 0xcd) ? BIT(1) : BIT(0);
> break;
> case QCOM_ID_IPQ5424:
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2026-10-01 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 4:33 [PATCH v2 0/3] Add few more SOC IDs for IPQ5210 family Kathiravan Thirumoorthy
2026-09-22 4:33 ` [PATCH v2 1/3] dt-bindings: arm: qcom,ids: add " Kathiravan Thirumoorthy
2026-09-28 6:00 ` Krzysztof Kozlowski
2026-09-22 4:33 ` [PATCH v2 2/3] soc: qcom: socinfo: " Kathiravan Thirumoorthy
2026-09-22 4:33 ` [PATCH v2 3/3] cpufreq: qcom-nvmem: add support for QCF3211 & IPQ5211 Kathiravan Thirumoorthy
2026-10-01 6:22 ` Viresh Kumar [this message]
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=ar38C5omDdaXQAID@vireshk-B250M-D3H \
--to=viresh.kumar@linaro.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@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