From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Landwerlin, Lionel G" <lionel.g.landwerlin@intel.com>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v7 6/8] drm/i915/uapi/pxp: Fix UAPI spec comments and add GET_PARAM for PXP
Date: Fri, 14 Apr 2023 15:17:59 +0000 [thread overview]
Message-ID: <ae72a0dfb157a9944434b773a93d82d40c7cb4e7.camel@intel.com> (raw)
In-Reply-To: <35d5f2da-115e-5873-1e3e-ba4db16537eb@intel.com>
Hi Lionel, does this patch work for you?
On Mon, 2023-04-10 at 10:22 -0700, Ceraolo Spurio, Daniele wrote:
> On 4/6/2023 10:44 AM, Alan Previn wrote:
alan:snip
> > +/*
> > + * Query the status of PXP support in i915.
> > + *
> > + * The query can fail in the following scenarios with the listed error codes:
> > + * -ENODEV = PXP support is not available on the GPU device or in the kernel
> > + * due to missing component drivers or kernel configs.
> > + * If the IOCTL is successful, the returned parameter will be set to one of the
> > + * following values:
> > + * 0 = PXP support maybe available but underlying SOC fusing, BIOS or firmware
> > + * configuration is unknown and a PXP-context-creation would be required
> > + * for final verification of feature availibility.
>
> Would it be useful to add:
>
> 1 = PXP support is available
>
> And start returning that after we've successfully created our first
> session? Not sure if userspace would use this though, since they still
> need to handle the 0 case anyway.
> I'm also ok with this patch as-is, as long as you get an ack from the
> userspace drivers for this interface behavior:
>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> Daniele
alan:snip
next prev parent reply other threads:[~2023-04-14 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 17:44 [Intel-gfx] [PATCH v7 0/8] drm/i915/pxp: Add MTL PXP Support Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 1/8] drm/i915/pxp: Add GSC-CS back-end resource init and cleanup Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 2/8] drm/i915/pxp: Add MTL hw-plumbing enabling for KCR operation Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 3/8] drm/i915/pxp: Add MTL helpers to submit Heci-Cmd-Packet to GSC Alan Previn
2023-04-10 16:10 ` Ceraolo Spurio, Daniele
2023-04-17 17:56 ` Teres Alexis, Alan Previn
2023-04-20 23:39 ` Ceraolo Spurio, Daniele
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 4/8] drm/i915/pxp: Add GSC-CS backend to send GSC fw messages Alan Previn
2023-04-10 16:28 ` Ceraolo Spurio, Daniele
2023-04-17 18:03 ` Teres Alexis, Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 5/8] drm/i915/pxp: Add ARB session creation and cleanup Alan Previn
2023-04-10 17:14 ` Ceraolo Spurio, Daniele
2023-04-17 18:21 ` Teres Alexis, Alan Previn
2023-04-17 19:15 ` Ceraolo Spurio, Daniele
2023-04-17 19:27 ` Teres Alexis, Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 6/8] drm/i915/uapi/pxp: Fix UAPI spec comments and add GET_PARAM for PXP Alan Previn
2023-04-10 17:22 ` Ceraolo Spurio, Daniele
2023-04-14 15:17 ` Teres Alexis, Alan Previn [this message]
2023-04-18 18:06 ` Lionel Landwerlin
2023-04-18 18:37 ` Teres Alexis, Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 7/8] drm/i915/pxp: On MTL, KCR enabling doesn't wait on tee component Alan Previn
2023-04-06 17:44 ` [Intel-gfx] [PATCH v7 8/8] drm/i915/pxp: Enable PXP with MTL-GSC-CS Alan Previn
2023-04-06 18:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pxp: Add MTL PXP Support (rev7) Patchwork
2023-04-06 18:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-06 18:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-07 9:53 ` [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=ae72a0dfb157a9944434b773a93d82d40c7cb4e7.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=rodrigo.vivi@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