From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Pin-yen Lin <treapking@chromium.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: "Chen-Yu Tsai" <wenst@chromium.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8192-asurada: Update min voltage constraint for Vgpu
Date: Wed, 13 Mar 2024 15:36:50 +0100 [thread overview]
Message-ID: <d1bdf9a6-3082-4076-99de-e49d59843244@collabora.com> (raw)
In-Reply-To: <20240313135157.98989-1-treapking@chromium.org>
Il 13/03/24 14:51, Pin-yen Lin ha scritto:
> Although the minimum voltage listed on the GPU OPP table is 606250 uV,
> the actual requested voltage could be even lower when the MTK Smart
> Voltage Scaling (SVS) driver is enabled.
>
> Set the minimum voltage to 300000 uV because it's supported by the
> regulator.
>
> Fixes: 3183cb62b033 ("arm64: dts: mediatek: asurada: Add SPMI regulators")
> Signed-off-by: Pin-yen Lin <treapking@chromium.org>
Okay, that makes sense, I agree.
...but.
The datasheet never mentions 0.3V as vmin - infact, it does mention that the
vsel is selected as (0V +) 6250 * Vsel, but the brief spec says that for the
standard configuration (in terms of HW), the Vmin is 0.4V and not 0.3.
Reading through makes me think that it's not much about the buck providing an
unstable output, but more about it starting to become inefficient under that
value.
This means that it is sensible to set, instead:
regulator-min-microvolt = <400000>;
Also, this is repeated on multiple platforms: can you please perform the same
change also on MT8183, MT8186 and MT8195?
P.S.: For MT6358, the Vmin for VGPU is 0.5V :-)
Cheers,
Angelo
> ---
>
> arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> index 43d80334610a..5cc5100a7c40 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> @@ -1448,7 +1448,7 @@ regulators {
> mt6315_7_vbuck1: vbuck1 {
> regulator-compatible = "vbuck1";
> regulator-name = "Vgpu";
> - regulator-min-microvolt = <606250>;
> + regulator-min-microvolt = <300000>;
> regulator-max-microvolt = <800000>;
> regulator-enable-ramp-delay = <256>;
> regulator-allowed-modes = <0 1 2>;
next prev parent reply other threads:[~2024-03-13 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 13:51 [PATCH] arm64: dts: mediatek: mt8192-asurada: Update min voltage constraint for Vgpu Pin-yen Lin
2024-03-13 14:36 ` AngeloGioacchino Del Regno [this message]
[not found] ` <CAHwYsiqJBsQn73H+2VeB4N3GNH=0EZ4qznqWwYCBjt6+qwNhHw@mail.gmail.com>
2024-03-14 10:02 ` AngeloGioacchino Del Regno
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=d1bdf9a6-3082-4076-99de-e49d59843244@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=treapking@chromium.org \
--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