[PATCH v8 6/8] drm/i915/uapi/pxp: Add a GET_PARAM for PXP
Jordan Justen
jordan.l.justen at intel.com
Wed Apr 26 22:35:54 UTC 2023
On 2023-04-26 11:17:16, Teres Alexis, Alan Previn wrote:
> alan: Hi Jordan, Tvrtko, Daniel Vetter and Lionel,...
> how to proceed on this series (which have required Rb/Ack's) in light of
> the recent discussion on the other series here:
> https://patchwork.freedesktop.org/patch/532994/?series=115980&rev=8
> it sounds like:
> - Jordan still wants the extension query
Yes, I do, but so far it doesn't appear that any kernel devs think
it's a reasonable request.
As I read through your emails about this pxp situation, it seems like
a separate issue. When I encountered the 8s delay, it was on MTL, and
apparently some firmware issue meant it was never going to work. So, I
thought this was a case of it either being supported, or never being
supported.
Now I'm seeing from your emails that in some cases it might be
supported, but just not ready yet. In that case a status which is
directly tied to pxp seems valuable. (But, yuck, how did we get into
this situation? :)
Can you tell that pxp is in progress, but not ready yet, as a separate
state from 'it will never work on this platform'? If so, maybe the
status could return something like:
0: It's never going to work
1: It's ready to use
2: It's starting and should work soon
I could see an argument for treating that as a case where we could
still advertise protected content support, but if we try to use it we
might be in for a nasty delay.
Maybe Lionel would have a different opinion on whether it would be a
good idea to go this route.
Regarding the extensions list I was requesting, it might be easiest
for the kernel if it just replies with all the extensions it knows
about regardless of whether they are usable right now.
-Jordan
More information about the dri-devel
mailing list