From: Marek Vasut <marek.vasut@mailbox.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: dri-devel@lists.freedesktop.org, David Airlie <airlied@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Simona Vetter <simona@ffwll.ch>,
etnaviv@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/etnaviv: add HWDB entry for GC8000 Nano Ultra VIP r6205
Date: Tue, 4 Nov 2025 22:34:07 +0100 [thread overview]
Message-ID: <4ac9dd98-adc8-4be9-9f5c-4e653f656453@mailbox.org> (raw)
In-Reply-To: <CAH9NwWdkjpV5YHmOpuCE=f7RVm1kXzqAOgN6=Sx1s-wxO_SGGA@mail.gmail.com>
On 11/4/25 4:50 PM, Christian Gmeiner wrote:
>>> This is the GPU/NPU combined device found on the ST STM32MP25 SoC.
>>> Feature bits taken from the downstream kernel driver 6.4.21.
>>>
>>> Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
>>
>> Acked-by: Christian Gmeiner <cgmeiner@igalia.com>
>>
>>> ---
>>> Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
>>> Cc: David Airlie <airlied@gmail.com>
>>> Cc: Lucas Stach <l.stach@pengutronix.de>
>>> Cc: Simona Vetter <simona@ffwll.ch>
>>> Cc: dri-devel@lists.freedesktop.org
>>> Cc: etnaviv@lists.freedesktop.org
>>> Cc: linux-kernel@vger.kernel.org
>>> ---
>>> drivers/gpu/drm/etnaviv/etnaviv_hwdb.c | 32 ++++++++++++++++++++++++++
>>> 1 file changed, 32 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/etnaviv/etnaviv_hwdb.c b/drivers/gpu/drm/etnaviv/etnaviv_hwdb.c
>>> index 8665f2658d51b..32d710baf17fe 100644
>>> --- a/drivers/gpu/drm/etnaviv/etnaviv_hwdb.c
>>> +++ b/drivers/gpu/drm/etnaviv/etnaviv_hwdb.c
>>> @@ -196,6 +196,38 @@ static const struct etnaviv_chip_identity etnaviv_chip_identities[] = {
>>> .minor_features10 = 0x90044250,
>>> .minor_features11 = 0x00000024,
>>> },
>>> + {
>>> + .model = 0x8000,
>>> + .revision = 0x6205,
>>> + .product_id = 0x80003,
>>> + .customer_id = 0x15,
>>> + .eco_id = 0,
>>> + .stream_count = 16,
>>> + .register_max = 64,
>>> + .thread_count = 512,
>>> + .shader_core_count = 2,
>>> + .nn_core_count = 2,
>>> + .vertex_cache_size = 16,
>>> + .vertex_output_buffer_size = 1024,
>>> + .pixel_pipes = 1,
>>> + .instruction_count = 512,
>>> + .num_constants = 320,
>>> + .buffer_size = 0,
>>> + .varyings_count = 16,
>>> + .features = 0xe0287c8d,
>>> + .minor_features0 = 0xc1799eff,
>>> + .minor_features1 = 0xfefbfad9,
>>> + .minor_features2 = 0xeb9d4fbf,
>>> + .minor_features3 = 0xedfffced,
>>> + .minor_features4 = 0xdb0dafc7,
>>> + .minor_features5 = 0x7b5ac333,
>>> + .minor_features6 = 0xfcce6000,
>>> + .minor_features7 = 0x03fbfa6f,
>>> + .minor_features8 = 0x00ef0ef0,
>>> + .minor_features9 = 0x0eca703c,
>>> + .minor_features10 = 0x898048f0,
>>> + .minor_features11 = 0x00000034,
>>> + },
>>> {
>>> .model = 0x8000,
>>> .revision = 0x7120,
>>> --
>>> 2.51.0
>>>
>>
>
> Applied to drm-misc-next.
Thank you.
I _think_ I will try to respin the flop reset patchset next.
next prev parent reply other threads:[~2025-11-04 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:30 Marek Vasut
2025-09-30 12:43 ` Christian Gmeiner
2025-11-04 15:50 ` Christian Gmeiner
2025-11-04 21:34 ` Marek Vasut [this message]
2025-11-05 13:44 ` Christian Gmeiner
2025-11-07 3:07 ` Marek Vasut
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=4ac9dd98-adc8-4be9-9f5c-4e653f656453@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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®