From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
To: intel-xe@lists.freedesktop.org, janga.rahul.kumar@intel.com,
ramadevi.gandi@intel.com
Cc: matthew.d.roper@intel.com, lucas.demarchi@intel.com
Subject: [PATCH v5 0/2] drm/xe/mocs: Add debugfs node to dump mocs
Date: Sat, 4 May 2024 01:09:00 +0530 [thread overview]
Message-ID: <20240503193902.2056202-1-janga.rahul.kumar@intel.com> (raw)
This is useful to check mocs configuration. Tests/Tools can use
this debugfs entry to get mocs info.
v2: Address review comments. Change debugfs output style similar
to pat debugfs. (Lucas De Marchi)
v3: rebase.
v4: Address review comments. Use function pointer inside ops
struct. Update Test-with links. Remove usage of flags wherever
not required. Create separate patch for moving function. (Lucas De Marchi)
v5: Address review comments. Move register defines. Modify mocs
info struct to avoid holes. (Lucas De Marchi)
Test-with: https://patchwork.freedesktop.org/patch/msgid/20240424200856.1194881-2-janga.rahul.kumar@intel.com
https://patchwork.freedesktop.org/patch/msgid/20240424200856.1194881-3-janga.rahul.kumar@intel.com/
Tested-on: ADL, DG1, DG2, MTL, PVC, LNL
Cc: Matt Roper <matthew.d.roper@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
Janga Rahul Kumar (2):
drm/xe: Relocate regs_are_mcr function
drm/xe/mocs: Add debugfs node to dump mocs
drivers/gpu/drm/xe/regs/xe_gt_regs.h | 38 +++-
drivers/gpu/drm/xe/xe_gt_debugfs.c | 11 +
drivers/gpu/drm/xe/xe_mocs.c | 299 +++++++++++++++++++++++----
drivers/gpu/drm/xe/xe_mocs.h | 8 +
4 files changed, 314 insertions(+), 42 deletions(-)
--
2.25.1
next reply other threads:[~2024-05-03 19:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:39 Janga Rahul Kumar [this message]
2024-05-03 19:39 ` [PATCH v5 1/2] drm/xe: Relocate regs_are_mcr function Janga Rahul Kumar
2024-05-03 19:39 ` [PATCH v5 2/2] drm/xe/mocs: Add debugfs node to dump mocs Janga Rahul Kumar
2024-05-06 14:48 ` Lucas De Marchi
2024-05-04 0:16 ` ✓ CI.Patch_applied: success for drm/xe/mocs: Add debugfs node to dump mocs (rev5) Patchwork
2024-05-04 0:17 ` ✓ CI.checkpatch: " Patchwork
2024-05-04 0:18 ` ✓ CI.KUnit: " Patchwork
2024-05-04 0:31 ` ✓ CI.Build: " Patchwork
2024-05-04 0:34 ` ✓ CI.Hooks: " Patchwork
2024-05-04 0:36 ` ✓ CI.checksparse: " Patchwork
2024-05-04 1:29 ` ✗ CI.BAT: failure " Patchwork
2024-05-04 5:45 ` ✓ CI.Patch_applied: success for drm/xe/mocs: Add debugfs node to dump mocs (rev6) Patchwork
2024-05-04 5:45 ` ✓ CI.checkpatch: " Patchwork
2024-05-04 5:46 ` ✓ CI.KUnit: " Patchwork
2024-05-04 5:58 ` ✓ CI.Build: " Patchwork
2024-05-04 6:00 ` ✓ CI.Hooks: " Patchwork
2024-05-04 6:02 ` ✓ CI.checksparse: " Patchwork
2024-05-04 6:35 ` ✓ CI.BAT: " Patchwork
2024-05-06 7:13 ` ✓ CI.FULL: success for drm/xe/mocs: Add debugfs node to dump mocs (rev5) Patchwork
2024-05-06 7:18 ` ✗ CI.FULL: failure for drm/xe/mocs: Add debugfs node to dump mocs (rev6) Patchwork
2024-05-06 16:34 ` [PATCH v5 0/2] drm/xe/mocs: Add debugfs node to dump mocs Lucas De Marchi
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=20240503193902.2056202-1-janga.rahul.kumar@intel.com \
--to=janga.rahul.kumar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=ramadevi.gandi@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).