Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniels@collabora.com>
To: igt-dev@lists.freedesktop.org
Cc: boris.brezillon@collabora.com, laura.nao@collabora.com,
	adrian.larumbe@collabora.com, daniel.almeida@collabora.com,
	liviu.dudau@arm.com
Subject: [PATCH 0/4] Add Panthor compute-shader test
Date: Thu, 15 Oct 2026 14:05:45 +0100	[thread overview]
Message-ID: <20261015130837.710795-1-daniels@collabora.com> (raw)

Hi,
This series adds a test to the Panthor suite to exercise a simple
compute shader. Whilst the existing group_submit test does validate that
we're able to execute CSF commands, it doesn't validate that we can use
this to actually run any shaders. This series should help as minimal
bringup and validation, inspired by a platform which was able to pass
group_submit just fine, but would immediately wedge the firmware when
trying to run a compute-shader test.

I don't plan to extend this much further - at least not with more
complex GPU command types or shader ISA, since that would require a lot
more divergent per-arch code to deal with changes in descriptor tables
and commands - but it does ensure that we can actually schedule and
execute jobs on a GPU.

Tested on v10 (RK3588), v13 (MT8196), and v14 (Lumex CSS FVP).

Cheers,
Daniel


             reply	other threads:[~2026-10-15 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 13:05 Daniel Stone [this message]
2026-10-15 13:05 ` [PATCH 1/4] panthor: Use all available GPU cores Daniel Stone
2026-10-15 15:50   ` Kamil Konieczny
2026-10-15 13:05 ` [PATCH 2/4] panthor: Add igt_panthor_get_arch() helper Daniel Stone
2026-10-15 15:52   ` Kamil Konieczny
2026-10-15 13:05 ` [PATCH 3/4] panthor: Add more CSF instructions Daniel Stone
2026-10-15 15:55   ` Kamil Konieczny
2026-10-15 13:05 ` [PATCH 4/4] panthor: Add simple compute-shader test Daniel Stone
2026-10-15 16:06   ` Kamil Konieczny

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=20261015130837.710795-1-daniels@collabora.com \
    --to=daniels@collabora.com \
    --cc=adrian.larumbe@collabora.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel.almeida@collabora.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=laura.nao@collabora.com \
    --cc=liviu.dudau@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