From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: matthias.bgg@gmail.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wenst@chromium.org,
alyssa.rosenzweig@collabora.com, nfraprado@collabora.com,
dmitry.osipenko@collabora.com
Subject: Re: [PATCH v3] soc: mediatek: Introduce mediatek-regulator-coupler driver
Date: Tue, 13 Sep 2022 14:08:54 +0200 [thread overview]
Message-ID: <ca89b96f-cb17-e6b0-5dcd-fede79737770@collabora.com> (raw)
In-Reply-To: <20220628120224.81180-1-angelogioacchino.delregno@collabora.com>
Il 28/06/22 14:02, AngeloGioacchino Del Regno ha scritto:
> This driver currently deals with GPU-SRAM regulator coupling, ensuring
> that the SRAM voltage is always between a specific range of distance to
> the GPU voltage, depending on the SoC, necessary in order to achieve
> system stability across the full range of supported GPU frequencies.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Hello Matthias,
gentle ping for this one, as it has been tested for quite a while here,
on multiple MediaTek SoCs, and it's working as expected.
Can we get it upstream? Is there any blocker?
Cheers,
Angelo
> ---
>
> Changes in v3:
> - Added braces to else-if branch
>
> Changes in v2:
> - Added check for n_coupled
> - Added check for vgpu to enforce attaching to vgpu<->sram coupling only
>
> Context:
> This driver is one of the pieces of a bigger puzzle, aiming to finally
> enable Dynamic Voltage/Frequency Scaling for Mali GPUs found on MediaTek
> SoCs on the fully open source graphics stack (Panfrost driver).
>
> No devicetree bindings are provided because this does not require any
> driver-specific binding at all.
>
> Last but not least: it was chosen to have this driver enabled for
> ( ARCH_MEDIATEK && REGULATOR ) without really giving a free configuration
> choice because, once the DVFS mechanism will be fully working, using one
> of the listed MediaTek SoCs *without* this coupling mechanism *will* lead
> to unstabilities and system crashes.
> For COMPILE_TEST, choice is given for obvious reasons.
>
prev parent reply other threads:[~2022-09-13 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:02 AngeloGioacchino Del Regno
2022-09-13 12:08 ` AngeloGioacchino Del Regno [this message]
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=ca89b96f-cb17-e6b0-5dcd-fede79737770@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dmitry.osipenko@collabora.com \
--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
all inboxes | Powered by JetHome®