Re: [PATCH v7 3/4] cpufreq: qcom-nvmem: Enable cpufreq for ipq5424

[Varadarajan Narayanan]

On Mon, Aug 11, 2025 at 02:52:02PM +0530, Viresh Kumar wrote:
> On 11-08-25, 14:39, Varadarajan Narayanan wrote:
> > From: Md Sadre Alam <quic_mdalam@xxxxxxxxxxx>
> >
> > IPQ5424 have different OPPs available for the CPU based on
> > SoC variant. This can be determined through use of an eFuse
> > register present in the silicon.
> >
> > Added support for ipq5424 on nvmem driver which helps to
> > determine OPPs at runtime based on the eFuse register which
> > has the CPU frequency limits. opp-supported-hw dt binding
> > can be used to indicate the available OPPs for each limit.
> >
> > nvmem driver also creates the "cpufreq-dt" platform_device after
> > passing the version matching data to the OPP framework so that the
> > cpufreq-dt handles the actual cpufreq implementation.
> >
> > Signed-off-by: Md Sadre Alam <quic_mdalam@xxxxxxxxxxx>
> > Signed-off-by: Sricharan Ramabadhran <quic_srichara@xxxxxxxxxxx>
> > Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> > Reviewed-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx>
> > [ Changed '!=' based check to '==' based check ]
> > Signed-off-by: Varadarajan Narayanan <quic_varada@xxxxxxxxxxx>
> > ---
> > v5: Add 'Acked-by: Viresh Kumar'
> > ---
> >  drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> >  drivers/cpufreq/qcom-cpufreq-nvmem.c | 5 +++++
> >  2 files changed, 6 insertions(+)
>
> You should have dropped this one now, as I already applied the
> previous version.

Sorry. Should I send a v8 with this dropped or is it okay?

Thanks
Varada