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 v2] drm/xe/oa: Expose media OA units
Date: Fri, 16 May 2025 17:10:58 -0700 [thread overview]
Message-ID: <87msbc6qr1.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250516204750.2135983-2-ashutosh.dixit@intel.com>
On Fri, 16 May 2025 13:47:51 -0700, Ashutosh Dixit wrote:
>
> static u32 __hwe_oam_unit(struct xe_hw_engine *hwe)
> {
> - if (GRAPHICS_VERx100(gt_to_xe(hwe->gt)) >= 1270) {
> - /*
> - * There's 1 SAMEDIA gt and 1 OAM per SAMEDIA gt. All media slices
> - * within the gt use the same OAM. All MTL/LNL SKUs list 1 SA MEDIA
> - */
> - xe_gt_WARN_ON(hwe->gt, hwe->gt->info.type != XE_GT_TYPE_MEDIA);
> + if (GRAPHICS_VERx100(gt_to_xe(hwe->gt)) < 1270)
> + return 0;
Will change this to 'return XE_OA_UNIT_INVALID;' in the next revision.
> static int xe_oa_init_oa_units(struct xe_oa *oa)
> {
> struct xe_gt *gt;
> int i, ret;
>
> + /* Needed for OAM implemenation here */
Will also fix the implementation spelling flagged by checkpatch in the next
revision.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2025-05-17 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 20:47 [PATCH v2] drm/xe/oa: Expose media OA units Ashutosh Dixit
2025-05-16 20:53 ` ✓ CI.Patch_applied: success for drm/xe/oa: Expose media OA units (rev2) Patchwork
2025-05-16 20:53 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-16 20:54 ` ✓ CI.KUnit: success " Patchwork
2025-05-16 21:05 ` ✓ CI.Build: " Patchwork
2025-05-16 21:07 ` ✓ CI.Hooks: " Patchwork
2025-05-16 21:09 ` ✓ CI.checksparse: " Patchwork
2025-05-16 21:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-17 0:10 ` Dixit, Ashutosh [this message]
2025-05-18 2:40 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27 4:08 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-27 4:08 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-27 4:10 ` ✓ CI.KUnit: success " Patchwork
2025-05-27 4:20 ` ✓ CI.Build: " 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=87msbc6qr1.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