Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH] drm/xe/oa: Expose media OA units
Date: Fri, 16 May 2025 11:17:01 -0700	[thread overview]
Message-ID: <87plg8774y.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250516180913.2072293-1-ashutosh.dixit@intel.com>

On Fri, 16 May 2025 11:09:13 -0700, Ashutosh Dixit wrote:
>
> +	/*
> +	 * XE_OAM_UNIT_SAG has only GSCCS attached to it, but only on some platforms. Also
> +	 * GSCCS cannot be used to submit batches to program the OAM unit. Therefore we don't
> +	 * assign an OA unit to GSCCS. This means that XE_OAM_UNIT_SAG is exposed as an OA
> +	 * unit without attached engines. However OA streams can still be opened on it.
> +	 */

Note that with this patch, OA streams can only be opened on the SCMI OAM
units, not on the OAM-SAG unit. To enable opening streams on OAM-SAG more
changes are needed (since OAM-SAG doesn't have an engine attached to
it). This work will be done via follow up patches.

Thanks.
--
Ashutosh

  reply	other threads:[~2025-05-16 18:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 18:09 [PATCH] drm/xe/oa: Expose media OA units Ashutosh Dixit
2025-05-16 18:17 ` Dixit, Ashutosh [this message]
2025-05-16 19:43 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-16 19:43 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-16 19:44 ` ✓ CI.KUnit: success " Patchwork
2025-05-16 19:55 ` ✓ CI.Build: " Patchwork
2025-05-16 19:57 ` ✓ CI.Hooks: " Patchwork
2025-05-16 19:59 ` ✓ CI.checksparse: " Patchwork
2025-05-16 20:23 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-05-18  0:14 ` ✗ Xe.CI.Full: " 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=87plg8774y.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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