linux-kernel - Re: [PATCH] arm64: dts: imx8mm-venice-gw7901: add cpu-supply node for cpufreq

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] [day] [month] [year] [list]

Message-ID: <20230717000945.GC9559@dragon>
Date:   Mon, 17 Jul 2023 08:09:45 +0800
From:   Shawn Guo <shawnguo@...nel.org>
To:     Tim Harvey <tharvey@...eworks.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        Li Yang <leoyang.li@....com>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: dts: imx8mm-venice-gw7901: add cpu-supply node
 for cpufreq

On Wed, Jul 12, 2023 at 09:13:49AM -0700, Tim Harvey wrote:
> On Tue, Jun 6, 2023 at 8:32 AM Tim Harvey <tharvey@...eworks.com> wrote:
> >
> > Add regulator config for cpu-supply in order to support cpufreq.
> >
> > Signed-off-by: Tim Harvey <tharvey@...eworks.com>
> > ---
> >  .../dts/freescale/imx8mm-venice-gw7901.dts     | 18 +++++++++++++++++-
> >  1 file changed, 17 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mm-venice-gw7901.dts b/arch/arm64/boot/dts/freescale/imx8mm-venice-gw7901.dts
> > index df3b2c93d2d5..d022b5807a24 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mm-venice-gw7901.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mm-venice-gw7901.dts
> > @@ -242,6 +242,22 @@ reg_wifi: regulator-wifi {
> >         };
> >  };
> >
> > +&A53_0 {
> > +       cpu-supply = <&buck2>;
> > +};
> > +
> > +&A53_1 {
> > +       cpu-supply = <&buck2>;
> > +};
> > +
> > +&A53_2 {
> > +       cpu-supply = <&buck2>;
> > +};
> > +
> > +&A53_3 {
> > +       cpu-supply = <&buck2>;
> > +};
> > +
> >  &ddrc {
> >         operating-points-v2 = <&ddrc_opp_table>;
> >
> > @@ -511,7 +527,7 @@ BUCK1 {
> >                         };
> >
> >                         /* vdd_arm: 0.805-1.0V (typ=0.9V) */
> > -                       BUCK2 {
> > +                       buck2: BUCK2 {
> >                                 regulator-name = "buck2";
> >                                 regulator-min-microvolt = <700000>;
> >                                 regulator-max-microvolt = <1300000>;
> > --
> > 2.25.1
> >
> 
> Hi Shawn,
> 
> I noticed this and several other of my pending patches delegated to
> you got marked as 'archived' and no longer appear as new in my
> patchwork queue [1]. I wanted to make sure they are still in your
> queue or see if I need to resubmit them. I'm not sure what the process
> is that you follow and if they got archived by you or something else.
> Please let me know if I need to do anything:

I do not use patchwork, so it doesn't reflect any status on my side.

Shawn