From: Steven Price <steven.price@arm.com>
To: Daniel Almeida <daniel.almeida@collabora.com>,
adrinael@adrinael.net, arek@hiler.eu,
kamil.konieczny@linux.intel.com, 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
Cc: intel-gfx@lists.freedesktop.org, igt-dev@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 1/4] lib: add support for opening Panthor devices
Date: Thu, 28 Aug 2025 16:39:23 +0100 [thread overview]
Message-ID: <2f9336f7-898e-4fe9-a17e-b41042de4d13@arm.com> (raw)
In-Reply-To: <20250828130402.2549948-2-daniel.almeida@collabora.com>
On 28/08/2025 14:03, Daniel Almeida wrote:
> We will be adding tests for Panthor in a subsequent patch, so first add
> the ability to open the device.
>
> Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
There's also chipset_to_str() which should be updated to return the
correct name. Although I think that only makes some error messages prettier.
I'm not familiar enough with IGT to really provide a proper review, but
I gave the tests a spin. See my comments on patch 4 for the bugs I hit ;)
Steve
> ---
> lib/drmtest.c | 1 +
> lib/drmtest.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/lib/drmtest.c b/lib/drmtest.c
> index 436b6de78..f4b429048 100644
> --- a/lib/drmtest.c
> +++ b/lib/drmtest.c
> @@ -220,6 +220,7 @@ static const struct module {
> { DRIVER_INTEL, "i915", modprobe_i915 },
> { DRIVER_MSM, "msm" },
> { DRIVER_PANFROST, "panfrost" },
> + { DRIVER_PANTHOR, "panthor" },
> { DRIVER_V3D, "v3d" },
> { DRIVER_VC4, "vc4" },
> { DRIVER_VGEM, "vgem" },
> diff --git a/lib/drmtest.h b/lib/drmtest.h
> index 27e5a18e2..1a933eae1 100644
> --- a/lib/drmtest.h
> +++ b/lib/drmtest.h
> @@ -55,6 +55,7 @@ int __get_drm_device_name(int fd, char *name, int name_size);
> #define DRIVER_MSM (1 << 6)
> #define DRIVER_XE (1 << 7)
> #define DRIVER_VMWGFX (1 << 8)
> +#define DRIVER_PANTHOR (1 << 9)
>
> /*
> * Exclude DRVER_VGEM from DRIVER_ANY since if you run on a system
next prev parent reply other threads:[~2025-08-28 15:39 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 [this message]
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
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=2f9336f7-898e-4fe9-a17e-b41042de4d13@arm.com \
--to=steven.price@arm.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=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@intel.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;
as well as URLs for NNTP newsgroup(s).