Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aurelien Jarno" <aurelien@aurel32.net>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/3] riscv: dts: spacemit: Add cpu scaling for Milk-V Jupiter
Date: Tue, 28 Jul 2026 21:19:58 +0000	[thread overview]
Message-ID: <20260728211959.4174F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728211020.1248676-2-aurelien@aurel32.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but wiring it up to cpufreq makes it a serious hardware safety risk: the CPU supply regulator (`buck1_0v9`) has an overly permissive maximum voltage constraint of 3.45V, which could physically damage the CPU.
--

--- Patch [1]: [PATCH 1/3] riscv: dts: spacemit: Add cpu scaling for Milk-V Jupiter ---
commit 4e25fb96470d1ad37415e03a27de699ef1f0da26
Author: Aurelien Jarno <aurelien@aurel32.net>

riscv: dts: spacemit: Add cpu scaling for Milk-V Jupiter

This commit enables CPU DVFS on the Milk-V Jupiter board by including the OPP
tables and wiring the CPU nodes to the CPU regulator supply.

> diff --git a/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts b/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
> index b61f5995ec771..3c16d0c20050e 100644
> --- a/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
[ ... ]
> @@ -107,6 +108,38 @@ &combo_phy {
>  	status = "okay";
>  };
>  
> +&cpu_0 {
> +	cpu-supply = <&buck1_0v9>;
> +};
[ ... ]
> @@ -209,7 +242,7 @@ pmic@41 {
>  		dldoin2-supply = <&buck5>;
>  
>  		regulators {
> -			buck1 {
> +			buck1_0v9: buck1 {
>  				regulator-min-microvolt = <500000>;
>  				regulator-max-microvolt = <3450000>;

[Severity: High]
This is a pre-existing issue, but by wiring up the CPU supply for cpufreq in 
this patch, does it introduce a severe hardware safety risk?

The buck1_0v9 regulator retains a very permissive maximum voltage constraint 
of 3.45V. Because the safe physical limit for the CPU is 1.05V (as defined in 
k1-opp.dtsi), could this permanently damage the hardware if a kernel bug, opp 
misconfiguration, or privileged userspace requests a higher voltage up to the 
board-defined maximum?

Should the board-level constraint be clamped to the safe physical limits of 
the CPU (e.g., 1050000 microvolts) to prevent the regulator from supplying a 
destructive voltage?

>  				regulator-ramp-delay = <5000>;
>  				regulator-always-on;
>  			};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260728211020.1248676-1-aurelien@aurel32.net?part=1

  reply	other threads:[~2026-07-28 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260728211020.1248676-1-aurelien@aurel32.net>
2026-07-28 21:05 ` [PATCH 1/3] riscv: dts: spacemit: Add cpu scaling for Milk-V Jupiter Aurelien Jarno
2026-07-28 21:19   ` sashiko-bot [this message]
2026-07-28 21:05 ` [PATCH 2/3] riscv: dts: spacemit: Add a common board dtsi for Milk-V Jupiter boards Aurelien Jarno
2026-07-28 21:23   ` sashiko-bot
2026-07-28 21:05 ` [PATCH 3/3] riscv: dts: spacemit: Add Milk-V Jupiter board (M1) Aurelien Jarno
2026-07-28 21:28   ` sashiko-bot

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=20260728211959.4174F1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=aurelien@aurel32.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox