devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: matthias.bgg@gmail.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v4 12/19] arm64: dts: mediatek: mt8192-asurada: Couple VGPU and VSRAM_OTHER regulators
Date: Thu, 2 Mar 2023 11:17:14 +0100	[thread overview]
Message-ID: <5dba27e1-d480-ea24-c1ba-03bb7f77b1b1@collabora.com> (raw)
In-Reply-To: <CAGXv+5GHdtbheL6wxtDo-szk+=3BGk2z93SBowd4Z=E9XupZkw@mail.gmail.com>

Il 02/03/23 11:03, Chen-Yu Tsai ha scritto:
> On Wed, Mar 1, 2023 at 5:55 PM AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com> wrote:
>>
>> Add coupling for these regulators, as VSRAM_OTHER is used to power the
>> GPU SRAM, and they have a strict voltage output relation to satisfy in
>> order to ensure GPU stable operation.
>> While at it, also add voltage constraint overrides for the GPU SRAM
>> regulator "mt6359_vsram_others" so that we stay in a safe range of
>> 0.75-0.80V.
>>
>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> ---
>>   arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
>> index 8570b78c04a4..f858eca219d7 100644
>> --- a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
>> +++ b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
>> @@ -447,6 +447,13 @@ &mt6359_vrf12_ldo_reg {
>>          regulator-always-on;
>>   };
>>
>> +&mt6359_vsram_others_ldo_reg {
>> +       regulator-min-microvolt = <750000>;
>> +       regulator-max-microvolt = <800000>;
>> +       regulator-coupled-with = <&mt6315_7_vbuck1>;
>> +       regulator-coupled-max-spread = <10000>;
> 
> Looking again at the downstream OPP table, it seems there's no voltage
> difference requirement. It only needs V_SRAM >= V_GPU. Same applies to
> MT8195. Looks like only MT8183 and MT8186 need V_SRAM - V_GPU >= 10000.

On MT8195 we don't need any regulator coupling. There, the GPU-SRAM voltage
is fixed at .. I don't remember, 0.7V? - anyway - MT8195 doesn't need to
scale the vsram.

> 
> Would setting max-spread to 0 work? I ask because with both regulator's
> maximum voltage set to 0.8V, there's no way we can reach the highest
> OPP.
> 

No that doesn't work. I can raise the Vgpu max voltage to 0.88V to solve the
issue right here and right now, or we can leave it like that and revisit it
later.

I would at this point go for setting mt6315_7_vbuck1's max-microvolt to
880000, as this is the maximum recommended voltage for the GPU as per the
MT8192 datasheet, it would also make sense as we would be still describing
the hardware in a correct manner.

What do you think?

Angelo

> ChenYu
> 
> 
>> +};
>> +
>>   &mt6359_vufs_ldo_reg {
>>          regulator-always-on;
>>   };
>> @@ -1411,6 +1418,8 @@ mt6315_7_vbuck1: vbuck1 {
>>                                  regulator-max-microvolt = <800000>;
>>                                  regulator-enable-ramp-delay = <256>;
>>                                  regulator-allowed-modes = <0 1 2>;
>> +                               regulator-coupled-with = <&mt6359_vsram_others_ldo_reg>;
>> +                               regulator-coupled-max-spread = <10000>;
>>                          };
>>                  };
>>          };
>> --
>> 2.39.2
>>

-- 
AngeloGioacchino Del Regno
Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718


  reply	other threads:[~2023-03-02 10:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  9:55 [PATCH v4 00/19] Enable GPU with DVFS support on MediaTek SoCs AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 01/19] arm64: dts: mediatek: mt8183-kukui: Couple VGPU and VSRAM_GPU regulators AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 02/19] arm64: dts: mediatek: mt8183-kukui: Override vgpu/vsram_gpu constraints AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 03/19] arm64: dts: mediatek: mt8183: Remove second opp-microvolt entries from gpu table AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 04/19] arm64: dts: mt8183-pumpkin: Couple VGPU and VSRAM_GPU regulators AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 05/19] arm64: dts: mediatek: mt8183-evb: " AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 06/19] arm64: dts: mediatek: mt8183: Use mediatek,mt8183b-mali as GPU compatible AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 07/19] arm64: dts: mediatek: mt8192: Add GPU nodes AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 08/19] arm64: dts: mediatek: mt8192: Add mfg_ref_sel clock to MFG0 domain AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 09/19] arm64: dts: mediatek: mt8192-asurada: Add MFG0 domain supply AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 10/19] arm64: dts: mediatek: mt8192-asurada: Assign sram supply to MFG1 pd AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 11/19] arm64: dts: mediatek: mt8192-asurada: Fix voltage constraint for Vgpu AngeloGioacchino Del Regno
2023-03-02  9:57   ` Chen-Yu Tsai
2023-03-01  9:55 ` [PATCH v4 12/19] arm64: dts: mediatek: mt8192-asurada: Couple VGPU and VSRAM_OTHER regulators AngeloGioacchino Del Regno
2023-03-02 10:03   ` Chen-Yu Tsai
2023-03-02 10:17     ` AngeloGioacchino Del Regno [this message]
2023-03-03  4:09       ` Chen-Yu Tsai
2023-03-07  9:24         ` Chen-Yu Tsai
2023-03-07  9:30           ` AngeloGioacchino Del Regno
2023-03-07  9:44             ` Chen-Yu Tsai
2023-03-07  9:47               ` AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 13/19] arm64: dts: mediatek: mt8192-asurada: Enable GPU AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 14/19] arm64: dts: mediatek: mt8195: Add mfg_core_tmp clock to MFG1 domain AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 15/19] arm64: dts: mt8195: Add panfrost node for Mali-G57 Valhall Natt GPU AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 16/19] arm64: dts: mediatek: mt8195-cherry: Enable Mali-G57 GPU AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 17/19] arm64: dts: mediatek: mt8186: Add GPU node AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 18/19] arm64: dts: mediatek: mt8183-pumpkin: Override vgpu/vsram_gpu constraints AngeloGioacchino Del Regno
2023-03-01  9:55 ` [PATCH v4 19/19] arm64: dts: mediatek: mt8183-evb: " AngeloGioacchino Del Regno
2023-03-02  9:36 ` [PATCH v4 00/19] Enable GPU with DVFS support on MediaTek SoCs Matthias Brugger
2023-03-02 10:10   ` AngeloGioacchino Del Regno
2023-03-02 10:11     ` Chen-Yu Tsai
2023-03-02 11:28       ` Matthias Brugger
2023-03-07  9:27         ` Chen-Yu Tsai
2023-03-07  9:37           ` AngeloGioacchino Del Regno
2023-03-23 10:36           ` AngeloGioacchino Del Regno
2023-03-30  7:49 ` Matthias Brugger

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=5dba27e1-d480-ea24-c1ba-03bb7f77b1b1@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.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=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).