All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-kernel@vger.kernel.org, Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	"open list:RISC-V ARCHITECTURE:Keyword:riscv"
	<linux-riscv@lists.infradead.org>,
	"open list:RISC-V SPACEMIT SoC Support:Keyword:spacemit"
	<spacemit@lists.linux.dev>
Subject: Re: [PATCH 0/6] riscv: dts: spacemit: fix maximum CPU core voltage for K1 boards
Date: Thu, 30 Jul 2026 08:24:25 +0000	[thread overview]
Message-ID: <20260730082425-GKJ76518@kernel.org> (raw)
In-Reply-To: <20260729150722.1598630-1-aurelien@aurel32.net>

On 17:02 Wed 29 Jul     , Aurelien Jarno wrote:
> The SpacemiT K1 based boards use the SpacemiT P1 PMIC. The buck1 and
> buck2 voltage regulators supply the CPU core voltage. They are
> configured with a maximum output voltage of 3.45V, while the highest
> operating point requires only 1.050V. This means that a kernel bug, OPP
> misconfiguration, or privileged userspace could request a voltage above
> the safe operating limit, causing possible permanent CPU damage.
> 
> This patch series set the maximum regulator voltage to 1.050V instead.
> There is one patch per board in order to ease backporting to older
> kernel versions.
> 
> Aurelien Jarno (6):
>   riscv: dts: spacemit: k1-bananapi-f3: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-milkv-jupiter: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-orangepi-rv2: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-musepi-pro: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-orangepi-r2s: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-bananapi-cm6: fix maximum CPU core voltage
> 
>  arch/riscv/boot/dts/spacemit/k1-bananapi-cm6.dtsi | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts   | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts    | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts  | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts  | 4 ++--
>  6 files changed, 12 insertions(+), 12 deletions(-)
> 

Reviewed-by: Yixun Lan <dlan@kernel.org>

-- 
Yixun Lan (dlan)

WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-kernel@vger.kernel.org, Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	"open list:RISC-V ARCHITECTURE:Keyword:riscv"
	<linux-riscv@lists.infradead.org>,
	"open list:RISC-V SPACEMIT SoC Support:Keyword:spacemit"
	<spacemit@lists.linux.dev>
Subject: Re: [PATCH 0/6] riscv: dts: spacemit: fix maximum CPU core voltage for K1 boards
Date: Thu, 30 Jul 2026 08:24:25 +0000	[thread overview]
Message-ID: <20260730082425-GKJ76518@kernel.org> (raw)
In-Reply-To: <20260729150722.1598630-1-aurelien@aurel32.net>

On 17:02 Wed 29 Jul     , Aurelien Jarno wrote:
> The SpacemiT K1 based boards use the SpacemiT P1 PMIC. The buck1 and
> buck2 voltage regulators supply the CPU core voltage. They are
> configured with a maximum output voltage of 3.45V, while the highest
> operating point requires only 1.050V. This means that a kernel bug, OPP
> misconfiguration, or privileged userspace could request a voltage above
> the safe operating limit, causing possible permanent CPU damage.
> 
> This patch series set the maximum regulator voltage to 1.050V instead.
> There is one patch per board in order to ease backporting to older
> kernel versions.
> 
> Aurelien Jarno (6):
>   riscv: dts: spacemit: k1-bananapi-f3: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-milkv-jupiter: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-orangepi-rv2: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-musepi-pro: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-orangepi-r2s: fix maximum CPU core voltage
>   riscv: dts: spacemit: k1-bananapi-cm6: fix maximum CPU core voltage
> 
>  arch/riscv/boot/dts/spacemit/k1-bananapi-cm6.dtsi | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts   | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts    | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts  | 4 ++--
>  arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts  | 4 ++--
>  6 files changed, 12 insertions(+), 12 deletions(-)
> 

Reviewed-by: Yixun Lan <dlan@kernel.org>

-- 
Yixun Lan (dlan)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-07-30  8:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 15:02 [PATCH 0/6] riscv: dts: spacemit: fix maximum CPU core voltage for K1 boards Aurelien Jarno
2026-07-29 15:02 ` Aurelien Jarno
2026-07-29 15:02 ` [PATCH 1/6] riscv: dts: spacemit: k1-bananapi-f3: fix maximum CPU core voltage Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-29 15:19   ` sashiko-bot
2026-07-29 15:02 ` [PATCH 2/6] riscv: dts: spacemit: k1-milkv-jupiter: " Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-29 15:14   ` sashiko-bot
2026-07-29 15:02 ` [PATCH 3/6] riscv: dts: spacemit: k1-orangepi-rv2: " Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-29 15:02 ` [PATCH 4/6] riscv: dts: spacemit: k1-musepi-pro: " Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-29 15:02 ` [PATCH 5/6] riscv: dts: spacemit: k1-orangepi-r2s: " Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-29 15:15   ` sashiko-bot
2026-07-29 15:02 ` [PATCH 6/6] riscv: dts: spacemit: k1-bananapi-cm6: " Aurelien Jarno
2026-07-29 15:02   ` Aurelien Jarno
2026-07-30  8:24 ` Yixun Lan [this message]
2026-07-30  8:24   ` [PATCH 0/6] riscv: dts: spacemit: fix maximum CPU core voltage for K1 boards Yixun Lan

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=20260730082425-GKJ76518@kernel.org \
    --to=dlan@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=aurelien@aurel32.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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.