dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: adrinael@adrinael.net, arek@hiler.eu,
	juhapekka.heikkila@gmail.com, bhanuprakash.modem@gmail.com,
	ashutosh.dixit@intel.com, karthik.b.s@intel.com,
	boris.brezillon@collabora.com, liviu.dudau@arm.com,
	steven.price@arm.com, intel-gfx@lists.freedesktop.org,
	igt-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/4] Add initial Panthor tests
Date: Fri, 29 Aug 2025 13:48:23 +0200	[thread overview]
Message-ID: <20250829114823.kxqjjrqdanbywsb6@kamilkon-DESK.igk.intel.com> (raw)
In-Reply-To: <20250828130402.2549948-1-daniel.almeida@collabora.com>

Hi Daniel,
On 2025-08-28 at 10:03:56 -0300, Daniel Almeida wrote:
> 
> This series adds basic Panthor tests. In particular, these are being
> used to test both Panthor and Tyr, i.e.: the new Rust GPU driver that
> implements Panthor's uAPI. Most of the initial tests were chosen in

Could you give link(s) to both driver and uAPI? Preferably on
lore.kernel.org. Also could you write which real hardware GPUs
are tested?

> order to have something to test Tyr with, but this series lays the
> groundwork so that more interesting tests can be added to test more of
> Panthor itself.

Imho you could also write this paragraph in you first patch
for drmtest.

> 
> Also, please note that this is my first IGT patch, so apologies in
> advance in case I forgot to follow any IGT-specific workflow when
> submitting this. I don't see a checkpatch.pl equivalent, so there was
> nothing to check this submission with as far as I am aware.

There is info about patchwork in CONTRIBUTING.md, you could just
reuse kernel one. Also there is config .checkpatch.conf in IGTs.

Regards,
Kamil

> 
> Daniel Almeida (4):
>   lib: add support for opening Panthor devices
>   tests: panthor: add initial infrastructure
>   lib: initial panthor infrastructure
>   tests/panthor: add panthor tests
> 
>  lib/drmtest.c                 |   1 +
>  lib/drmtest.h                 |   1 +
>  lib/igt_panthor.c             | 150 +++++++++++++++++++
>  lib/igt_panthor.h             |  28 ++++
>  lib/meson.build               |   1 +
>  meson.build                   |   8 ++
>  tests/meson.build             |   2 +
>  tests/panthor/meson.build     |  15 ++
>  tests/panthor/panthor_gem.c   |  59 ++++++++
>  tests/panthor/panthor_group.c | 264 ++++++++++++++++++++++++++++++++++
>  tests/panthor/panthor_query.c |  25 ++++
>  tests/panthor/panthor_vm.c    |  73 ++++++++++
>  12 files changed, 627 insertions(+)
>  create mode 100644 lib/igt_panthor.c
>  create mode 100644 lib/igt_panthor.h
>  create mode 100644 tests/panthor/meson.build
>  create mode 100644 tests/panthor/panthor_gem.c
>  create mode 100644 tests/panthor/panthor_group.c
>  create mode 100644 tests/panthor/panthor_query.c
>  create mode 100644 tests/panthor/panthor_vm.c
> 
> -- 
> 2.50.1
> 

      parent reply	other threads:[~2025-08-29 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 13:03 [PATCH i-g-t 0/4] Add initial Panthor tests Daniel Almeida
2025-08-28 13:03 ` [PATCH i-g-t 1/4] lib: add support for opening Panthor devices Daniel Almeida
2025-08-28 15:39   ` Steven Price
2025-08-29 11:35     ` Kamil Konieczny
2025-08-28 13:03 ` [PATCH i-g-t 2/4] tests: panthor: add initial infrastructure Daniel Almeida
2025-08-28 13:03 ` [PATCH i-g-t 3/4] lib: initial panthor infrastructure Daniel Almeida
2025-08-29 11:42   ` Kamil Konieczny
2025-08-28 13:04 ` [PATCH i-g-t 4/4] tests/panthor: add panthor tests Daniel Almeida
2025-08-28 15:39   ` Steven Price
2025-08-29 11:31   ` Kamil Konieczny
2025-08-28 14:01 ` [PATCH i-g-t 0/4] Add initial Panthor tests Boris Brezillon
2025-08-29 11:46 ` Juha-Pekka Heikkilä
2025-08-29 11:48 ` Kamil Konieczny [this message]

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=20250829114823.kxqjjrqdanbywsb6@kamilkon-DESK.igk.intel.com \
    --to=kamil.konieczny@linux.intel.com \
    --cc=adrinael@adrinael.net \
    --cc=arek@hiler.eu \
    --cc=ashutosh.dixit@intel.com \
    --cc=bhanuprakash.modem@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.com \
    --cc=karthik.b.s@intel.com \
    --cc=liviu.dudau@arm.com \
    --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).