From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Robert Marko <robimarko@gmail.com>
Cc: rafael@kernel.org, ilia.lin@kernel.org, agross@kernel.org,
andersson@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
ansuelsmth@gmail.com
Subject: Re: [PATCH 1/2] cpufreq: qcom-nvmem: add support for IPQ8074
Date: Fri, 2 Jun 2023 10:54:29 +0200 [thread overview]
Message-ID: <ab8d7a2d-e2db-39cd-dbac-bb5535cb8c19@linaro.org> (raw)
In-Reply-To: <20230602041327.klyjs4cevmzn6vs7@vireshk-i7>
On 2.06.2023 06:13, Viresh Kumar wrote:
> On 30-05-23, 18:54, Robert Marko wrote:
>> IPQ8074 comes in 2 families:
>> * IPQ8070A/IPQ8071A (Acorn) up to 1.4GHz
>> * IPQ8072A/IPQ8074A/IPQ8076A/IPQ8078A (Hawkeye) up to 2.2GHz
>>
>> So, in order to be able to share one OPP table lets add support for IPQ8074
>> family based of SMEM SoC ID-s as speedbin fuse is always 0 on IPQ8074.
>>
>> IPQ8074 compatible is blacklisted from DT platdev as the cpufreq device
>> will get created by NVMEM CPUFreq driver.
>>
>> Signed-off-by: Robert Marko <robimarko@gmail.com>
>
> I am waiting for someone from Qcom to review this stuff.
We're on v2 and it looks like there will be a v3
https://lore.kernel.org/linux-arm-msm/20230530165807.642084-1-robimarko@gmail.com/
Konrad
>
prev parent reply other threads:[~2023-06-02 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 16:54 [PATCH 1/2] cpufreq: qcom-nvmem: add support for IPQ8074 Robert Marko
2023-05-30 16:54 ` [PATCH 2/2] cpufreq: qcom-nvmem: add support for IPQ8064 Robert Marko
2023-06-02 4:13 ` [PATCH 1/2] cpufreq: qcom-nvmem: add support for IPQ8074 Viresh Kumar
2023-06-02 8:54 ` Konrad Dybcio [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=ab8d7a2d-e2db-39cd-dbac-bb5535cb8c19@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=ilia.lin@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=robimarko@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.