From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: wens@kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: allwinner: h6: orangepi: Enable CPU frequency scaling
Date: Sun, 15 Nov 2026 18:01:33 +0100 [thread overview]
Message-ID: <hUUAMPreQkqgr8nLJGKykw@gmail.com> (raw)
In-Reply-To: <CAGb2v66acxKq7HR=p+ky7dhT03fTXct1_82dPXu5ebS-fYgpvA@mail.gmail.com>
Dne nedelja, 15. november 2026 ob 16:09:23 Srednjeevropski standardni čas je Chen-Yu Tsai napisal(a):
> On Sun, Nov 15, 2026 at 9:22 PM Jernej Skrabec <jernej.skrabec@gmail.com> wrote:
> >
> > The Orange Pi One Plus and Lite2 lack the CPU OPP table and CPU supply,
> > so the CPU never scales its frequency. Add both, like on Orange Pi 3.
> > OPPs above the regulator constraints stay unused.
>
> My review agent noted that some of the other boards raised the constraints
> when CPU DVFS was enabled. Do you think it's reasonable to do the same
> for the OrangePi? Or do you want to be more conservative?
Yes, I'll prepare patches for raising constraints.
Best regards,
Jernej
>
> Note that I already applied this series.
>
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
> > ---
> > arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> > index 40c5c42b347e..a2a2e4cb0256 100644
> > --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi.dtsi
> > @@ -5,6 +5,7 @@
> > /dts-v1/;
> >
> > #include "sun50i-h6.dtsi"
> > +#include "sun50i-h6-cpu-opp.dtsi"
> > #include "sun50i-h6-gpu-opp.dtsi"
> >
> > #include <dt-bindings/gpio/gpio.h>
> > @@ -65,6 +66,10 @@ reg_vcc5v: vcc5v {
> > };
> > };
> >
> > +&cpu0 {
> > + cpu-supply = <®_dcdca>;
> > +};
> > +
> > &de {
> > status = "okay";
> > };
> > --
> > 2.43.0
> >
>
next prev parent reply other threads:[~2026-11-15 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 13:22 [PATCH v2 0/3] arm64: dts: allwinner: h6: Enable GPU and CPU DVFS on more boards Jernej Skrabec
2026-11-15 13:22 ` [PATCH v2 1/3] arm64: dts: allwinner: h6: orangepi: Add regulator ramp delays Jernej Skrabec
2026-11-15 13:22 ` [PATCH v2 2/3] arm64: dts: allwinner: h6: Add GPU OPP table to all boards Jernej Skrabec
2026-11-15 13:22 ` [PATCH v2 3/3] arm64: dts: allwinner: h6: orangepi: Enable CPU frequency scaling Jernej Skrabec
2026-11-15 15:09 ` Chen-Yu Tsai
2026-11-15 17:01 ` Jernej Škrabec [this message]
2026-11-15 15:07 ` [PATCH v2 0/3] arm64: dts: allwinner: h6: Enable GPU and CPU DVFS on more boards Chen-Yu Tsai
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=hUUAMPreQkqgr8nLJGKykw@gmail.com \
--to=jernej.skrabec@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@kernel.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.