From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/4] drm/xe: Unify IP descriptors
Date: Thu, 20 Feb 2025 14:25:07 -0300 [thread overview]
Message-ID: <20250220172532.66613-1-gustavo.sousa@intel.com> (raw)
The Xe driver has support, official or not, for both pre-GMDID and
GMDID-based IPs. For each type, we have been using a different approach
for describing instances:
- For pre-GMDID ones, we fully describe the IP via struct
xe_{graphics,media}_desc.
- For GMDID-based ones, we have IP info separated in different data
structures: instances of xe_{graphics,media}_desc are used to describe
IP names and features; while instances of gmdid_map effectively fully
describe the IPs, by mapping IP versions to descriptors.
In this series I propose that we use a unified approach to describe IPs:
- struct xe_{graphics,media}_desc purpose becomes to only describe
features of the IP and can be reused across releases if possible (the
latter is already done with the current approach);
- struct gmdid_map is turned into struct xe_ip, to fully describe an IP;
- the field "name" is moved from xe_{graphics,media}_desc to xe_ip,
making the former specifically about the features while xe_ip
incorporates features and release info.
Gustavo Sousa (4):
drm/xe: Set IP names in functions handling IP version
drm/xe: Disambiguate GMDID-based IP names
drm/xe: Rename gmdid_map to xe_ip
drm/xe: Convert pre-GMDID IPs to struct xe_ip
drivers/gpu/drm/xe/tests/xe_pci.c | 24 +++---
drivers/gpu/drm/xe/xe_pci.c | 118 +++++++++++++++---------------
drivers/gpu/drm/xe/xe_pci_types.h | 15 +---
3 files changed, 77 insertions(+), 80 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-20 17:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 17:25 Gustavo Sousa [this message]
2025-02-20 17:25 ` [PATCH 1/4] drm/xe: Set IP names in functions handling IP version Gustavo Sousa
2025-02-20 20:40 ` Matt Roper
2025-02-20 17:25 ` [PATCH 2/4] drm/xe: Disambiguate GMDID-based IP names Gustavo Sousa
2025-02-20 20:45 ` Matt Roper
2025-02-20 17:25 ` [PATCH 3/4] drm/xe: Rename gmdid_map to xe_ip Gustavo Sousa
2025-02-20 20:52 ` Matt Roper
2025-02-20 17:25 ` [PATCH 4/4] drm/xe: Convert pre-GMDID IPs to struct xe_ip Gustavo Sousa
2025-02-20 21:10 ` Matt Roper
2025-02-20 21:23 ` Gustavo Sousa
2025-02-20 21:25 ` Gustavo Sousa
2025-02-20 21:31 ` Matt Roper
2025-02-20 18:02 ` ✓ CI.Patch_applied: success for drm/xe: Unify IP descriptors Patchwork
2025-02-20 18:02 ` ✓ CI.checkpatch: " Patchwork
2025-02-20 18:03 ` ✓ CI.KUnit: " Patchwork
2025-02-20 18:20 ` ✓ CI.Build: " Patchwork
2025-02-20 18:22 ` ✓ CI.Hooks: " Patchwork
2025-02-20 18:23 ` ✓ CI.checksparse: " Patchwork
2025-02-20 18:55 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-21 12:53 ` ✗ Xe.CI.Full: failure " Patchwork
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=20250220172532.66613-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.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