From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "ustonli@chromium.org" <ustonli@chromium.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"ri-devel@lists.freedesktop.org" <ri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v9 6/8] drm/i915/uapi/pxp: Add a GET_PARAM for PXP
Date: Tue, 9 May 2023 13:27:34 +0000 [thread overview]
Message-ID: <9226d87084ed5702f4c700e93bcf41e1e24f16bb.camel@intel.com> (raw)
In-Reply-To: <e40f2b8750b39facd98f72cda63bc733ca0319d5.camel@intel.com>
>
alan:snip
> > [Jordan:]
> > Another option besides from the timeout loop in
> > iris_create_hw_context() might be to check I915_PARAM_PXP_STATUS after
> > the context create fails to tweak the debug message.
> alan: Yeah, that is an option - I'm thinking we can add a DBG that reads
> either "PXP context failure expected due not ready" vs
> "Unexpected PXP context failure"
Hi Jordan, should i proceed this way? (I can repost the UMD patch accordingly)
next prev parent reply other threads:[~2023-05-09 13:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 23:48 [Intel-gfx] [PATCH v9 0/8] drm/i915/pxp: Add MTL PXP Support Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 1/8] drm/i915/pxp: Add GSC-CS back-end resource init and cleanup Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 2/8] drm/i915/pxp: Add MTL hw-plumbing enabling for KCR operation Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 3/8] drm/i915/pxp: Add MTL helpers to submit Heci-Cmd-Packet to GSC Alan Previn
2023-04-28 0:22 ` Teres Alexis, Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 4/8] drm/i915/pxp: Add GSC-CS backend to send GSC fw messages Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 5/8] drm/i915/pxp: Add ARB session creation and cleanup Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 6/8] drm/i915/uapi/pxp: Add a GET_PARAM for PXP Alan Previn
2023-05-05 5:30 ` Teres Alexis, Alan Previn
2023-05-05 7:39 ` Jordan Justen
2023-05-08 17:49 ` Teres Alexis, Alan Previn
2023-05-09 13:27 ` Teres Alexis, Alan Previn [this message]
2023-05-10 4:01 ` Teres Alexis, Alan Previn
2023-05-10 19:40 ` Souza, Jose
2023-05-10 20:24 ` Teres Alexis, Alan Previn
2023-05-10 21:38 ` Jordan Justen
2023-05-10 21:50 ` Jordan Justen
2023-05-10 22:00 ` Teres Alexis, Alan Previn
2023-05-10 22:24 ` Jordan Justen
2023-05-10 23:24 ` Teres Alexis, Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 7/8] drm/i915/pxp: On MTL, KCR enabling doesn't wait on tee component Alan Previn
2023-04-27 23:48 ` [Intel-gfx] [PATCH v9 8/8] drm/i915/pxp: Enable PXP with MTL-GSC-CS Alan Previn
2023-04-28 0:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pxp: Add MTL PXP Support (rev9) Patchwork
2023-04-28 0:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-28 0:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-28 5:34 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=9226d87084ed5702f4c700e93bcf41e1e24f16bb.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jordan.l.justen@intel.com \
--cc=ri-devel@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=ustonli@chromium.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