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: [RESEND PATCH v3] soc: mediatek: Introduce mediatek-regulator-coupler driver
Date: Fri, 4 Nov 2022 10:17:02 +0100 [thread overview]
Message-ID: <e739b1e0-7c07-0604-25bd-dfc711599608@collabora.com> (raw)
In-Reply-To: <20221006115816.66853-1-angelogioacchino.delregno@collabora.com>
Il 06/10/22 13:58, 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>
> ---
>
> This driver was successfully tested for more than 3 months.
> GPU DVFS works correctly with no stability issues.
>
Hey Matthias,
gentle ping for this one...
Cheers,
Angelo
next prev parent reply other threads:[~2022-11-04 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 11:58 [RESEND PATCH v3] soc: mediatek: Introduce mediatek-regulator-coupler driver AngeloGioacchino Del Regno
2022-10-06 12:36 ` Alyssa Rosenzweig
2022-11-04 9:17 ` AngeloGioacchino Del Regno [this message]
2022-11-21 11:44 ` Matthias Brugger
2022-11-21 12:01 ` AngeloGioacchino Del Regno
2022-12-16 13:15 ` AngeloGioacchino Del Regno
2022-12-16 15:26 ` Matthias Brugger
2022-12-19 8:49 ` AngeloGioacchino Del Regno
2023-01-10 9:06 ` AngeloGioacchino Del Regno
2023-01-30 10:28 ` 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=e739b1e0-7c07-0604-25bd-dfc711599608@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