linux-kernel - Re: [PATCH v6] cpufreq: qcom-nvmem: add support for IPQ8074

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOX2RU6K7h8Xc0SGK2CeOCaAaimKRf9eqhMYAaySXxQLZiUNtg@mail.gmail.com>
Date:   Mon, 16 Oct 2023 10:43:18 +0200
From:   Robert Marko <robimarko@...il.com>
To:     Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc:     Viresh Kumar <viresh.kumar@...aro.org>, rafael@...nel.org,
        agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
        ilia.lin@...nel.org, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v6] cpufreq: qcom-nvmem: add support for IPQ8074

On Mon, 16 Oct 2023 at 10:36, Dmitry Baryshkov
<dmitry.baryshkov@...aro.org> wrote:
>
> On Mon, 16 Oct 2023 at 11:29, Robert Marko <robimarko@...il.com> wrote:
> >
> > On Mon, 16 Oct 2023 at 10:22, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> > >
> > > On 16-10-23, 09:02, Viresh Kumar wrote:
> > > > On 13-10-23, 19:20, Robert Marko wrote:
> > > > > IPQ8074 comes in 3 families:
> > > > > * IPQ8070A/IPQ8071A (Acorn) up to 1.4GHz
> > > > > * IPQ8172/IPQ8173/IPQ8174 (Oak) 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@...il.com>
> > > > > Acked-by: Konrad Dybcio <konrad.dybcio@...aro.org>
> > > > > ---
> > > > > Changes in v6:
> > > > > * Split IPQ8074 from the IPQ8064 as IPQ8064 has additional dependencies.
> > > >
> > > > Applied. Thanks.
> > >
> > > And it failed to build, please fix it. Dropped from my tree now.
> >
> > I am looking at the error and it should not happen as the ID-s have
> > been in linux-next for a month now:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/dt-bindings/arm/qcom,ids.h?h=next-20231016&id=b8c889bef9797a58b8b5aad23875cc4d04b3efd3
> >
> > They are also part of Bjorns 6.7 driver PR:
> > https://lore.kernel.org/all/20231015204014.855672-1-andersson@kernel.org/T/
>
> But Bjorn's tree isn't a part of the cpufreq tree. In such cases it is
> typical to ask first maintainer to create an immutable branch / tag,
> which can later be also merged into another tree without going into
> troubles of merging the whole tree of the irrelevant subsystem.

Ok, I understand now, the thing is that the ID-s were added for
socinfo initially but recently
I finally had somebody with access to the Oak HW so I added them to
cpufreq as well.

What can I do to help this get resolved?

Regards,
Robert
>
>
> --
> With best wishes
> Dmitry