From: Chen-Yu Tsai <wenst@chromium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: airlied@gmail.com, daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, steven.price@arm.com,
alyssa.rosenzweig@collabora.com, matthias.bgg@gmail.com,
robh@kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 10/10] drm/panfrost: Add new compatible for Mali on the MT8183 SoC
Date: Wed, 22 Feb 2023 15:06:53 +0800 [thread overview]
Message-ID: <CAGXv+5FqZPXaE8tyEFtejsYpKMLzUt5R_QnkbQrDSBM_u7rRYg@mail.gmail.com> (raw)
In-Reply-To: <20230221153740.1620529-11-angelogioacchino.delregno@collabora.com>
On Tue, Feb 21, 2023 at 11:37 PM AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com> wrote:
>
> The "mediatek,mt8183-mali" compatible uses platform data that calls for
> getting (and managing) two regulators ("mali" and "sram") but devfreq
> does not support this usecase, resulting in DVFS not working.
>
> Since a lot of MediaTek SoCs need to set the voltages for the GPU SRAM
> regulator in a specific relation to the GPU VCORE regulator, a MediaTek
> SoC specific driver was introduced to automatically satisfy, through
> coupling, these constraints: this means that there is at all no need to
> manage both regulators in panfrost but to otherwise just manage the main
> "mali" (-> gpu vcore) regulator instead.
>
> Keeping in mind that we cannot break the ABI, the most sensible route
> (avoiding hacks and uselessly overcomplicated code) to get a MT8183
> node with one power supply was to add a new "mediatek,mt8183b-mali"
> compatible, which effectively deprecates the former.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Reviewed-by: Steven Price <steven.price@arm.com>
Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
next prev parent reply other threads:[~2023-02-22 7:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 15:37 [PATCH v2 00/10] Panfrost: Improve and add MediaTek SoCs support AngeloGioacchino Del Regno
2023-02-21 15:37 ` [PATCH v2 01/10] dt-bindings: gpu: mali-bifrost: Add power-domain-names to base schema AngeloGioacchino Del Regno
2023-02-21 15:37 ` [PATCH v2 02/10] dt-bindings: gpu: mali-bifrost: Split out MediaTek power-domains variation AngeloGioacchino Del Regno
2023-02-22 7:58 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 03/10] dt-bindings: gpu: mali-bifrost: Allow up to 5 power domains for MT8192 AngeloGioacchino Del Regno
2023-02-22 8:00 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 04/10] dt-bindings: gpu: mali-bifrost: Add compatible for MT8195 SoC AngeloGioacchino Del Regno
2023-02-22 8:01 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 05/10] dt-bindings: gpu: mali-bifrost: Add new MT8183 compatible AngeloGioacchino Del Regno
2023-02-22 8:01 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 06/10] dt-bindings: gpu: mali-bifrost: Add a compatible for MediaTek MT8186 AngeloGioacchino Del Regno
2023-02-22 8:37 ` Chen-Yu Tsai
2023-02-22 9:13 ` AngeloGioacchino Del Regno
2023-02-23 2:43 ` Chen-Yu Tsai
2023-02-23 13:15 ` AngeloGioacchino Del Regno
2023-02-21 15:37 ` [PATCH v2 07/10] drm/panfrost: Increase MAX_PM_DOMAINS to 5 AngeloGioacchino Del Regno
2023-02-22 4:38 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 08/10] drm/panfrost: Add the MT8192 GPU ID AngeloGioacchino Del Regno
2023-02-22 4:11 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 09/10] drm/panfrost: Add mediatek,mt8192-mali compatible AngeloGioacchino Del Regno
2023-02-22 4:39 ` Chen-Yu Tsai
2023-02-21 15:37 ` [PATCH v2 10/10] drm/panfrost: Add new compatible for Mali on the MT8183 SoC AngeloGioacchino Del Regno
2023-02-22 7:06 ` Chen-Yu Tsai [this message]
2023-02-22 7:55 ` [PATCH v2 00/10] Panfrost: Improve and add MediaTek SoCs support Chen-Yu Tsai
2023-02-22 8:39 ` Chen-Yu Tsai
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=CAGXv+5FqZPXaE8tyEFtejsYpKMLzUt5R_QnkbQrDSBM_u7rRYg@mail.gmail.com \
--to=wenst@chromium.org \
--cc=airlied@gmail.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.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=robh@kernel.org \
--cc=steven.price@arm.com \
/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).