Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH v3 0/1] drm/xe: Expose number of dss per group and helpers
Date: Mon, 29 Jan 2024 14:34:02 -0800	[thread overview]
Message-ID: <20240129223403.150578-1-zhanjun.dong@intel.com> (raw)

Expose helper for dss per group, features like GuC register
capture will need this info to prepare buffer required.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>
Cc: Stuart Summers <stuart.summers@intel.com>

Changes from prior revs:
v3: Rename functions with mcr removed
v2: Resend with cover letter

Zhanjun Dong (1):
  drm/xe: Expose number of dss per group and helpers

 drivers/gpu/drm/xe/xe_gt_mcr.c          | 40 ++++++++++++++++++++++++-
 drivers/gpu/drm/xe/xe_gt_mcr.h          | 17 +++++++++++
 drivers/gpu/drm/xe/xe_gt_topology.c     |  3 --
 drivers/gpu/drm/xe/xe_hw_engine_types.h |  3 ++
 4 files changed, 59 insertions(+), 4 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-01-29 22:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 22:34 Zhanjun Dong [this message]
2024-01-29 22:34 ` [PATCH v3 1/1] drm/xe: Expose number of dss per group and helpers Zhanjun Dong
2024-01-30 16:10   ` Summers, Stuart
2024-01-29 22:37 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-29 22:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-30 16:00   ` Summers, Stuart
2024-01-29 22:38 ` ✓ CI.KUnit: success " Patchwork
2024-01-29 22:45 ` ✓ CI.Build: " Patchwork
2024-01-29 22:46 ` ✗ CI.Hooks: failure " Patchwork
2024-01-30 15:59   ` Summers, Stuart
2024-01-29 22:47 ` ✓ CI.checksparse: success " Patchwork
2024-01-29 23:10 ` ✓ CI.BAT: " 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=20240129223403.150578-1-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@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