From: Chen-Yu Tsai <wens@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Samuel Holland <samuel@sholland.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] arm64: dts: allwinner: h6: Enable GPU and CPU DVFS on more boards
Date: Sun, 15 Nov 2026 23:07:22 +0800 [thread overview]
Message-ID: <179475524292.3273316.2909957727689381668.b4-ty@kernel.org> (raw)
In-Reply-To: <20261115132215.289236-1-jernej.skrabec@gmail.com>
On Sun, 15 Nov 2026 14:22:11 +0100, Jernej Skrabec wrote:
> Most H6 boards don't use the GPU OPP table, and the Orange Pi One Plus
> and Lite2 lack CPU DVFS as well, so their GPU and CPU run at a fixed
> clock rate. This series enables both.
>
> Changes in v2:
> - new patch 1: add regulator-ramp-delay to vdd-cpu and vdd-gpu on the
> Orange Pi One Plus and Lite2, like on the other AXP805-based H6 boards
>
> [...]
Applied to sunxi/dt-for-7.5 in sunxi, thanks!
[1/3] arm64: dts: allwinner: h6: orangepi: Add regulator ramp delays
https://git.kernel.org/sunxi/linux/c/6442683b687c
[2/3] arm64: dts: allwinner: h6: Add GPU OPP table to all boards
https://git.kernel.org/sunxi/linux/c/348a4f82f13b
[3/3] arm64: dts: allwinner: h6: orangepi: Enable CPU frequency scaling
https://git.kernel.org/sunxi/linux/c/6527dd6be62e
Best regards,
--
Chen-Yu Tsai <wens@kernel.org>
prev parent reply other threads:[~2026-11-15 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 13:22 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 15:07 ` Chen-Yu Tsai [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=179475524292.3273316.2909957727689381668.b4-ty@kernel.org \
--to=wens@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®