From: Steven Price <steven.price@arm.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Chen-Yu Tsai <wenst@chromium.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Cc: airlied@gmail.com, daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, 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 v3 08/11] drm/panfrost: Add the MT8192 GPU ID
Date: Fri, 24 Feb 2023 13:53:02 +0000 [thread overview]
Message-ID: <8c20f01a-2123-b76d-bf70-bf75aec9efb8@arm.com> (raw)
In-Reply-To: <61ebdd1a-2737-0516-08fd-3b9aa0ddd4fe@collabora.com>
On 24/02/2023 13:08, AngeloGioacchino Del Regno wrote:
> Il 24/02/23 11:06, Chen-Yu Tsai ha scritto:
>> On Thu, Feb 23, 2023 at 9:35 PM AngeloGioacchino Del Regno
>> <angelogioacchino.delregno@collabora.com> wrote:
>>>
>>> From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
>>>
>>> MediaTek MT8192 has a Mali-G57 with a special GPU ID. Add its GPU ID,
>>> but treat it as otherwise identical to a standard Mali-G57.
>>>
>>> We do _not_ fix up the GPU ID here -- userspace needs to be aware of the
>>> special GPU ID, in case we find functional differences between
>>> MediaTek's implementation and the standard Mali-G57 down the line.
>>>
>>> Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
>>> 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>
>>
>> As previously mentioned, MT8195 Mali G57 has minor revision number 1.
>> Do we need to handle that?
>>
>
> Maybe something went wrong while sending the reply to the same question
> on v2?
>
> Anyway, from what I can see on my MT8195 machine, it works fine without
> adding
> any particular handling...
>
> Alyssa, Steven,
> are you aware of anything that we should consider?
The minor revision means that the set of HW workarounds might be
different. Specifically it appears that "BASE_HW_ISSUE_TTRX_3485"
applies to G57 ('Natt') r0p0 but not r0p1.
That particular workaround is a horrendous "dummy job" in kbase and we
don't have an implementation in Panfrost. However Panfrost also doesn't
(yet[1]) proactively SOFT_STOP jobs so is also unlikely to be affected.
TLDR; Minor revision 1 has a HW bug fixed, Panfrost isn't affected by
the bug anyway.
Steve
[1] It's been on my todo list for a while to look at improving job
scheduling, but to be honest I doubt I'm going to get round to it with
Panfrost, and PanCSF obviously changes the job scheduling anyway.
> Regards,
> Angelo
>
>>> ---
>>> drivers/gpu/drm/panfrost/panfrost_gpu.c | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/panfrost/panfrost_gpu.c
>>> b/drivers/gpu/drm/panfrost/panfrost_gpu.c
>>> index 6452e4e900dd..d28b99732dde 100644
>>> --- a/drivers/gpu/drm/panfrost/panfrost_gpu.c
>>> +++ b/drivers/gpu/drm/panfrost/panfrost_gpu.c
>>> @@ -204,6 +204,14 @@ static const struct panfrost_model gpu_models[] = {
>>>
>>> GPU_MODEL(g57, 0x9001,
>>> GPU_REV(g57, 0, 0)),
>>> +
>>> + /* MediaTek MT8192 has a Mali-G57 with a different GPU ID
>>> from the
>>> + * standard. Arm's driver does not appear to handle this model.
>>> + * ChromeOS has a hack downstream for it. Treat it as
>>> equivalent to
>>> + * standard Mali-G57 for now.
>>> + */
>>> + GPU_MODEL(g57, 0x9003,
>>> + GPU_REV(g57, 0, 0)),
>>> };
>>>
>>> static void panfrost_gpu_init_features(struct panfrost_device *pfdev)
>>> --
>>> 2.39.2
>>>
>
>
next prev parent reply other threads:[~2023-02-24 13:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 13:34 [PATCH v3 00/11] Panfrost: Improve and add MediaTek SoCs support AngeloGioacchino Del Regno
2023-02-23 13:34 ` [PATCH v3 01/11] dt-bindings: gpu: mali-bifrost: Add power-domain-names to base schema AngeloGioacchino Del Regno
2023-02-24 10:15 ` Krzysztof Kozlowski
2023-02-23 13:34 ` [PATCH v3 02/11] dt-bindings: gpu: mali-bifrost: Split out MediaTek power-domains variation AngeloGioacchino Del Regno
2023-02-24 10:08 ` Chen-Yu Tsai
2023-02-24 10:09 ` Chen-Yu Tsai
2023-02-24 13:09 ` AngeloGioacchino Del Regno
2023-02-24 10:57 ` Krzysztof Kozlowski
2023-02-23 13:34 ` [PATCH v3 03/11] dt-bindings: gpu: mali-bifrost: Allow up to 5 power domains for MT8192 AngeloGioacchino Del Regno
2023-02-24 10:08 ` Chen-Yu Tsai
2023-02-23 13:34 ` [PATCH v3 04/11] dt-bindings: gpu: mali-bifrost: Add compatible for MT8195 SoC AngeloGioacchino Del Regno
2023-02-24 10:08 ` Chen-Yu Tsai
2023-02-27 13:19 ` AngeloGioacchino Del Regno
2023-02-23 13:34 ` [PATCH v3 05/11] dt-bindings: gpu: mali-bifrost: Add new MT8183 compatible AngeloGioacchino Del Regno
2023-02-24 10:07 ` Chen-Yu Tsai
2023-02-24 10:58 ` Krzysztof Kozlowski
2023-02-23 13:34 ` [PATCH v3 06/11] dt-bindings: gpu: mali-bifrost: Add support for MediaTek MT8186 AngeloGioacchino Del Regno
2023-02-24 10:06 ` Chen-Yu Tsai
2023-02-24 10:58 ` Krzysztof Kozlowski
2023-02-23 13:34 ` [PATCH v3 07/11] drm/panfrost: Increase MAX_PM_DOMAINS to 5 AngeloGioacchino Del Regno
2023-02-24 10:06 ` Chen-Yu Tsai
2023-02-23 13:34 ` [PATCH v3 08/11] drm/panfrost: Add the MT8192 GPU ID AngeloGioacchino Del Regno
2023-02-24 10:06 ` Chen-Yu Tsai
2023-02-24 13:08 ` AngeloGioacchino Del Regno
2023-02-24 13:53 ` Steven Price [this message]
2023-02-23 13:34 ` [PATCH v3 09/11] drm/panfrost: Add mediatek,mt8192-mali compatible AngeloGioacchino Del Regno
2023-02-24 10:04 ` Chen-Yu Tsai
2023-02-23 13:34 ` [PATCH v3 10/11] drm/panfrost: Add new compatible for Mali on the MT8183 SoC AngeloGioacchino Del Regno
2023-02-24 10:03 ` Chen-Yu Tsai
2023-02-23 13:34 ` [PATCH v3 11/11] drm/panfrost: Add support for Mali on the MT8186 SoC AngeloGioacchino Del Regno
2023-02-24 8:46 ` Steven Price
2023-02-24 10:03 ` Chen-Yu Tsai
2023-02-24 9:43 ` [PATCH v3 00/11] Panfrost: Improve and add MediaTek SoCs support 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=8c20f01a-2123-b76d-bf70-bf75aec9efb8@arm.com \
--to=steven.price@arm.com \
--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=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).