[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c82e4053-4cef-4010-a734-4dc537574201@quicinc.com>
Date: Wed, 6 Mar 2024 10:10:55 +0530
From: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konrad.dybcio@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof
Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley
<conor+dt@...nel.org>, Ilia Lin <ilia.lin@...nel.org>,
"Rafael J. Wysocki"
<rafael@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 3/3] cpufreq: qcom-nvmem: add support for IPQ5321
On 3/5/2024 10:05 AM, Viresh Kumar wrote:
> On 04-03-24, 12:42, Viresh Kumar wrote:
>> On 28-02-24, 20:21, Kathiravan Thirumoorthy wrote:
>>> Like all other SoCs in IPQ5332 family, cpufreq for IPQ5321 is also
>>> determined by the eFuse, with the maximum limit of 1.1GHz. Add support
>>> for the same.
>>>
>>> Signed-off-by: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>
>>> ---
>>> drivers/cpufreq/qcom-cpufreq-nvmem.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
>>> index ea05d9d67490..0a46b5d49d32 100644
>>> --- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
>>> +++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
>>> @@ -191,6 +191,7 @@ static int qcom_cpufreq_kryo_name_version(struct device *cpu_dev,
>>> case QCOM_ID_IPQ5312:
>>> case QCOM_ID_IPQ5302:
>>> case QCOM_ID_IPQ5300:
>>> + case QCOM_ID_IPQ5321:
>>> case QCOM_ID_IPQ9514:
>>> case QCOM_ID_IPQ9550:
>>> case QCOM_ID_IPQ9554:
>>
>> Applied. Thanks.
>
> Dropped since the previous commit it required too. Can we get the
> necessary acks for me to pick those ?
>
Sorry for not mentioning the dependencies.
patch 1/3 and 2/3 are already has the R-b and A-b tags. But typically
those patches will go via qcom tree. Do you want to pick it via your
tree? Sorry, I'm not sure on this...
Thanks,
Kathiravan T.
Powered by blists - more mailing lists