Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: mediatek: mt8192-asurada: Add ramp-delay for MT6315 regulators
Date: Fri, 30 Oct 2026 10:41:04 +0000	[thread overview]
Message-ID: <sashiko-outbox-190860@kernel.org> (raw)
In-Reply-To: <20261030103418.2355854-1-wenst@chromium.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: mediatek: swapped regulator-ramp-delay for Vbcpu and Vlcpu
--

commit 810dcac6146b830cb56f853c88e0887dc012ef9d
Author: Chen-Yu Tsai <wenst@chromium.org>

arm64: dts: mediatek: mt8192-asurada: Add ramp-delay for MT6315 regulators

This commit adds regulator-ramp-delay properties for the MT6315 buck
regulators (Vbcpu, Vlcpu, and Vgpu) on Asurada to ensure voltage increases
settle before switching CPU or GPU to higher operating points.

> diff --git a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> index 40d34b16dc807..68d84fc55767b 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> @@ -1500,6 +1500,7 @@ mt6315_6_vbuck1: vbuck1 {
>  				regulator-min-microvolt = <400000>;
>  				regulator-max-microvolt = <1193750>;
>  				regulator-enable-ramp-delay = <256>;
> +				regulator-ramp-delay = <4500>;
>  				regulator-allowed-modes = <0 1 2>;
>  				regulator-always-on;
>  			};
> @@ -1509,6 +1510,7 @@ mt6315_6_vbuck3: vbuck3 {
>  				regulator-min-microvolt = <400000>;
>  				regulator-max-microvolt = <1193750>;
>  				regulator-enable-ramp-delay = <256>;
> +				regulator-ramp-delay = <8000>;

[Severity: High]
Are the regulator-ramp-delay values for mt6315_6_vbuck1 and mt6315_6_vbuck3
swapped here?

The commit message states that the slew rates are 8000 uV/us for Vbcpu, and
4500 uV/us for Vlcpu and Vgpu. However, in mt8192-asurada.dtsi,
mt6315_6_vbuck1 is Vbcpu and mt6315_6_vbuck3 is Vlcpu:

	mt6315_6_vbuck1: vbuck1 {
		regulator-name = "Vbcpu";
		...
		regulator-ramp-delay = <4500>;
		...
	};

	mt6315_6_vbuck3: vbuck3 {
		regulator-name = "Vlcpu";
		...
		regulator-ramp-delay = <8000>;
		...
	};

Because mt6315_volt_range_ops does not implement .set_ramp_delay,
_regulator_set_voltage_time() uses constraints->ramp_delay directly to
compute the settling wait time during cpufreq DVFS transitions. Assigning
8000 to Vlcpu when its hardware slew rate is 4500 uV/us causes the regulator
core to wait for less than the required voltage ramp time before scaling the
little CPU cluster frequency up, while waiting longer than needed on Vbcpu.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261030103418.2355854-1-wenst@chromium.org?part=1

  parent reply	other threads:[~2026-10-30 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 10:34 [PATCH 1/3] arm64: dts: mediatek: mt8192-asurada: Add ramp-delay for MT6315 regulators Chen-Yu Tsai
2026-10-30 10:34 ` [PATCH 2/3] arm64: dts: mediatek: mt8195-cherry: Fix ramp-delay for Vgpu Chen-Yu Tsai
2026-10-30 10:34 ` [PATCH 3/3] arm64: dts: mediatek: mt8186-corsola-voltorb: Add MT6319 ramp-delay Chen-Yu Tsai
2026-10-30 10:41 ` sashiko-bot [this message]
2026-10-30 10:51   ` [PATCH 1/3] arm64: dts: mediatek: mt8192-asurada: Add ramp-delay for MT6315 regulators 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=sashiko-outbox-190860@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wenst@chromium.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