Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pin-yen Lin <treapking@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: linux-arm-kernel@lists.infradead.org,
	"Chen-Yu Tsai" <wenst@chromium.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
	linux-mediatek@lists.infradead.org,
	"Pin-yen Lin" <treapking@chromium.org>
Subject: [PATCH v2 0/4] Update Vgpu minimum voltage for MT8183, MT8186, MT8192, MT8195
Date: Fri, 15 Mar 2024 19:16:01 +0800	[thread overview]
Message-ID: <20240315111621.2263159-1-treapking@chromium.org> (raw)

Use the minimum voltage listed on the Vgpu regulator datasheets instead
of the minimum value on GPU OPP table. This is because the requested
voltage could be lower when the MTK Smart Voltage Scaling (SVS) driver
is enabled.

Also update the incorrect MT6315 regulator usages on MT8192 and MT8195.

Changes in v2:
- Update Vgpu min voltage for MT8183, MT8186, MT8195
- Fix other usages of MT6315 buck1/buck3

Pin-yen Lin (4):
  arm64: dts: mediatek: mt8192-asurada: Update min voltage constraint
    for MT6315
  arm64: dts: mediatek: mt8195-cherry: Update min voltage constraint for
    MT6315
  arm64: dts: mediatek: mt8183-kukui: Use default min voltage for MT6358
  arm64: dts: mediatek: mt8186-corsola: Update min voltage constraint
    for Vgpu

 arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi   | 1 -
 arch/arm64/boot/dts/mediatek/mt8186-corsola.dtsi | 2 +-
 arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 6 +++---
 arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi  | 4 ++--
 4 files changed, 6 insertions(+), 7 deletions(-)

-- 
2.44.0.291.gc1ea87d7ee-goog


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

             reply	other threads:[~2024-03-15 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 11:16 Pin-yen Lin [this message]
2024-03-15 11:16 ` [PATCH v2 1/4] arm64: dts: mediatek: mt8192-asurada: Update min voltage constraint for MT6315 Pin-yen Lin
2024-03-15 12:36   ` AngeloGioacchino Del Regno
2024-03-15 11:16 ` [PATCH v2 2/4] arm64: dts: mediatek: mt8195-cherry: " Pin-yen Lin
2024-03-15 12:36   ` AngeloGioacchino Del Regno
2024-03-15 11:16 ` [PATCH v2 3/4] arm64: dts: mediatek: mt8183-kukui: Use default min voltage for MT6358 Pin-yen Lin
2024-03-15 12:36   ` AngeloGioacchino Del Regno
2024-03-15 11:16 ` [PATCH v2 4/4] arm64: dts: mediatek: mt8186-corsola: Update min voltage constraint for Vgpu Pin-yen Lin
2024-03-15 12:36   ` AngeloGioacchino Del Regno
2024-04-03 10:30 ` [PATCH v2 0/4] Update Vgpu minimum voltage for MT8183, MT8186, MT8192, MT8195 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=20240315111621.2263159-1-treapking@chromium.org \
    --to=treapking@chromium.org \
    --cc=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=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