[Intel-gfx] [PULL] gvt-fixes

2020-11-16 Thread Zhenyu Wang
Hi, Here's more gvt fixes for 5.10. It temporarily disables VFIO edid feature on BXT/APL until its virtual display is really fixed to make it work properly. And fixes for DPCD 1.2 and error return in taking module reference. Thanks -- The following changes since commit 92010a97098c4c9fd777408cc9

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Handle max_bpc==16 (rev2)

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915: Handle max_bpc==16 (rev2) URL : https://patchwork.freedesktop.org/series/83711/ State : success == Summary == CI Bug Log - changes from CI_DRM_9338_full -> Patchwork_18916_full Summary --- **SUC

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Correctly set SFC capability for video engines (rev2)

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915: Correctly set SFC capability for video engines (rev2) URL : https://patchwork.freedesktop.org/series/83551/ State : failure == Summary == Applying: drm/i915: Correctly set SFC capability for video engines Using index info to reconstruct a base tree... M

Re: [Intel-gfx] [PATCH 23/23] drm/i915: Enable bigjoiner

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:58AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Enough plumbing should be in place to throw the bigjoiner switch. > > Signed-off-by: Ville Syrjälä Reviewed-by: Manasi Navare Manasi > --- > drivers/gpu/drm/i915/display/intel_dp.c | 3 --- > 1 file ch

Re: [Intel-gfx] [PATCH 22/23] drm/i915: Add bigjoiner state dump

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:57AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Add a big of bigjoiner information to the state dump. > > Signed-off-by: Ville Syrjälä Reviewed-by: Manasi Navare Manasi > --- > drivers/gpu/drm/i915/display/intel_display.c | 4 > 1 file changed,

Re: [Intel-gfx] [PATCH 21/23] drm/i915: Fix cursor src/dst rectangle with bigjoiner

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:56AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > We can't call drm_plane_state_src() this late for the slave plane since > it would consult the wrong uapi state. We've alreayd done the correct > uapi->hw copy earlier, so let's just preserve the unclipped sr

Re: [Intel-gfx] [PATCH 20/23] drm/i915: Disable legacy cursor fastpath for bigjoiner

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:55AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > The legacy cursor fastpath code doesn't deal with bigjoiner. > Disable the fastpath for now. > > Signed-off-by: Ville Syrjälä Reviewed-by: Manasi Navare Manasi > --- > drivers/gpu/drm/i915/display/inte

Re: [Intel-gfx] [PATCH 17/23] drm/i915: Get the uapi state from the correct plane when bigjoiner is used

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:52AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > When using bigjoiner userspace is only controlling the "master" > plane, so use its uapi state for the "slave" plane as well. > > hw.crtc needs a bit of magic since we don't want to copy that from > the uapi

Re: [Intel-gfx] [PATCH 16/23] drm/i915: Add planes affected by bigjoiner to the state

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:51AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Make sure both the bigjoiner "master" and "slave" plane are > in the state whenever either of them is in the state. > > Signed-off-by: Ville Syrjälä > --- > drivers/gpu/drm/i915/display/intel_display.c | 4

[Intel-gfx] [PATCH stable-5.4] drm/i915: Correctly set SFC capability for video engines

2020-11-16 Thread Daniele Ceraolo Spurio
From: Venkata Sandeep Dhanalakota Commit 5ce6861d36ed5207aff9e5eead4c7cc38a986586 upstream. This backport targets stable version 5.4, since the original patch fails to apply there, due to a variable having moved from one struct to another. The only change required for the patch to apply to 5.4 i

Re: [Intel-gfx] [PATCH 22/27] drm/i915/pxp: Expose session state for display protection flip

2020-11-16 Thread Huang, Sean Z
Hi Joonas, Thanks for your feedback! intel_pxp_gem_object_status() was used in the following commit "[27/27] drm/i915/pxp: Add plane decryption support", which belongs to the i915 display component instead of PXP. So personally I prefer not to merge this code commit with "[27/27] drm/i915/pxp

Re: [Intel-gfx] [PATCH 15/23] drm/i915: Add crtcs affected by bigjoiner to the state

2020-11-16 Thread Navare, Manasi
On Sat, Nov 14, 2020 at 12:03:50AM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Make sure both crtcs participating in the bigjoiner stuff > are in the state. > > Signed-off-by: Ville Syrjälä Reviewed-by: Manasi Navare Manasi > --- > drivers/gpu/drm/i915/display/intel_display.c | 2

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Fix wrong return value of perf_request_latency()

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix wrong return value of perf_request_latency() URL : https://patchwork.freedesktop.org/series/83891/ State : failure == Summary == CI Bug Log - changes from CI_DRM_9337_full -> Patchwork_18915_full =

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Fix wrong return value of perf_series_engines()

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix wrong return value of perf_series_engines() URL : https://patchwork.freedesktop.org/series/83890/ State : failure == Summary == CI Bug Log - changes from CI_DRM_9337_full -> Patchwork_18914_full ==

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/lspcon: enter standby mode to enhance power saving

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/lspcon: enter standby mode to enhance power saving URL : https://patchwork.freedesktop.org/series/83886/ State : failure == Summary == CI Bug Log - changes from CI_DRM_9337_full -> Patchwork_18913_full

Re: [Intel-gfx] [PATCH] drm/i915: Handle max_bpc==16

2020-11-16 Thread Souza, Jose
On Tue, 2020-11-10 at 23:04 +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > EDID can declare the maximum supported bpc up to 16, > and apparently there are displays that do so. Currently > we assume 12 bpc is tha max. Fix the assumption and > toss in a MISSING_CASE() for any other value we

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Handle max_bpc==16 (rev2)

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915: Handle max_bpc==16 (rev2) URL : https://patchwork.freedesktop.org/series/83711/ State : success == Summary == CI Bug Log - changes from CI_DRM_9338 -> Patchwork_18916 Summary --- **SUCCESS**

Re: [Intel-gfx] [PATCH v4 05/27] drm: fix some kernel-doc markups

2020-11-16 Thread Daniel Vetter
On Mon, Nov 16, 2020 at 01:37:11PM +0200, Jani Nikula wrote: > On Mon, 16 Nov 2020, Mauro Carvalho Chehab wrote: > > Some identifiers have different names between their prototypes > > and the kernel-doc markup. > > > > Others need to be fixed, as kernel-doc markups should use this format: > >

Re: [Intel-gfx] [PATCH i-g-t 4/5] lsgpu: Add filter type print-out selection

2020-11-16 Thread Zbigniew Kempczyński
On Mon, Nov 16, 2020 at 05:26:52PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > In the previous patch we switched the lsgpu output to a short and user > friendly format but some users will need a shorthand for getting other > types of device selection filters than the defaut drm. > >

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 5/5] intel_gpu_top: Default GPU list to PCI mode

2020-11-16 Thread Zbigniew Kempczyński
On Mon, Nov 16, 2020 at 05:26:53PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > It is more obvious for the user to only shows filters for DRM master > nodes since those are the ones that intel_gpu_top monitors. > > v2: > * Filter prefix needs to be sys: when listing PCI devices. > >

Re: [Intel-gfx] [PATCH i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Zbigniew Kempczyński
On Mon, Nov 16, 2020 at 05:26:51PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > After devices are sorted post scanning, assing a card index to each so it > can be easily accessed if PCI filter for a card needs to be printed out. > > v2: > * Preserve existing pci:..card=N behaviour. (

[Intel-gfx] [PATCH i-g-t 5/5] intel_gpu_top: Default GPU list to PCI mode

2020-11-16 Thread Tvrtko Ursulin
From: Tvrtko Ursulin It is more obvious for the user to only shows filters for DRM master nodes since those are the ones that intel_gpu_top monitors. v2: * Filter prefix needs to be sys: when listing PCI devices. Signed-off-by: Tvrtko Ursulin --- tools/intel_gpu_top.c | 3 ++- 1 file changed

[Intel-gfx] [PATCH i-g-t 4/5] lsgpu: Add filter type print-out selection

2020-11-16 Thread Tvrtko Ursulin
From: Tvrtko Ursulin In the previous patch we switched the lsgpu output to a short and user friendly format but some users will need a shorthand for getting other types of device selection filters than the defaut drm. Add some command line switches to enable this: $ lsgpu card0

[Intel-gfx] [PATCH i-g-t 2/5] lsgpu: User friendly device listing

2020-11-16 Thread Tvrtko Ursulin
From: Tvrtko Ursulin New default user frindly device listing mode which replaces: sys:/sys/devices/pci:00/:00:02.0/drm/card0 subsystem : drm drm card: /dev/dri/card0 parent : sys:/sys/devices/pci:00/:00:02.0 sys:/sys/devices/pci:00/:00:

[Intel-gfx] [PATCH i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Tvrtko Ursulin
From: Tvrtko Ursulin After devices are sorted post scanning, assing a card index to each so it can be easily accessed if PCI filter for a card needs to be printed out. v2: * Preserve existing pci:..card=N behaviour. (Zbigniew) Signed-off-by: Tvrtko Ursulin Cc: Petri Latvala Cc: Zbigniew Kemp

[Intel-gfx] [PATCH i-g-t 1/5] intel_gpu_top: User friendly device listing

2020-11-16 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Adding a new device selection print type suitable for user-facing use cases like intel_gpu_top -L and later lsgpu. Instead of: sys:/sys/devices/pci:00/:00:02.0/drm/card0 subsystem : drm drm card: /dev/dri/card0 parent : sys:/sys/de

Re: [Intel-gfx] [RFC i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Tvrtko Ursulin
On 16/11/2020 16:47, Zbigniew Kempczyński wrote: On Mon, Nov 16, 2020 at 03:09:43PM +, Tvrtko Ursulin wrote: + /* Core scanning function. * * All scanned devices are kept inside igt_devs.all pointer array. @@ -657,6 +685,7 @@ static void scan_drm_devices(void) udev_u

Re: [Intel-gfx] [RFC i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Zbigniew Kempczyński
On Mon, Nov 16, 2020 at 03:09:43PM +, Tvrtko Ursulin wrote: > > > + > > > /* Core scanning function. > > >* > > >* All scanned devices are kept inside igt_devs.all pointer array. > > > @@ -657,6 +685,7 @@ static void scan_drm_devices(void) > > > udev_unref(udev); > > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fix wrong return value of perf_request_latency()

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix wrong return value of perf_request_latency() URL : https://patchwork.freedesktop.org/series/83891/ State : success == Summary == CI Bug Log - changes from CI_DRM_9337 -> Patchwork_18915 S

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fix wrong return value of perf_series_engines()

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix wrong return value of perf_series_engines() URL : https://patchwork.freedesktop.org/series/83890/ State : success == Summary == CI Bug Log - changes from CI_DRM_9337 -> Patchwork_18914 Su

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/lspcon: enter standby mode to enhance power saving

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/lspcon: enter standby mode to enhance power saving URL : https://patchwork.freedesktop.org/series/83886/ State : success == Summary == CI Bug Log - changes from CI_DRM_9337 -> Patchwork_18913 Summary --

[Intel-gfx] [PATCH] drm/i915/selftests: Fix wrong return value of perf_request_latency()

2020-11-16 Thread Zhang Xiaoxu
If intel context create failed, the perf_request_latency() will return 0 rather than error, because we doesn't initialize the return value. Fixes: 25c26f18ea79 ("drm/i915/selftests: Measure dispatch latency") Reported-by: Hulk Robot Signed-off-by: Zhang Xiaoxu --- drivers/gpu/drm/i915/selftests

Re: [Intel-gfx] [PATCH 18/27] drm/i915/pxp: Implement funcs to create the TEE channel (fwd)

2020-11-16 Thread Julia Lawall
See line 81. julia -- Forwarded message -- Date: Sun, 15 Nov 2020 06:48:16 +0800 From: kernel test robot To: kbu...@lists.01.org Cc: l...@intel.com, Julia Lawall Subject: Re: [Intel-gfx] [PATCH 18/27] drm/i915/pxp: Implement funcs to create the TEE channel CC: kbuild-...@li

[Intel-gfx] [PATCH v4 05/27] drm: fix some kernel-doc markups

2020-11-16 Thread Mauro Carvalho Chehab
Some identifiers have different names between their prototypes and the kernel-doc markup. Others need to be fixed, as kernel-doc markups should use this format: identifier - description Signed-off-by: Mauro Carvalho Chehab --- drivers/gpu/drm/drm_atomic_state_helper.c | 2 +- driver

[Intel-gfx] [PATCH] drm/i915/selftests: Fix wrong return value of perf_series_engines()

2020-11-16 Thread Zhang Xiaoxu
If intel context create failed, the perf_series_engines() will return 0 rather than error, because we doesn't initialize the return value. Fixes: cbfd3a0c5a55 ("drm/i915/selftests: Add request throughput measurement to perf") Reported-by: Hulk Robot Signed-off-by: Zhang Xiaoxu --- drivers/gpu/

[Intel-gfx] [PATCH v4 00/27]Fix several bad kernel-doc markups

2020-11-16 Thread Mauro Carvalho Chehab
Kernel-doc has always be limited to a probably bad documented rule: The kernel-doc markups should appear *imediatelly before* the function or data structure that it documents. On other words, if a C file would contain something like this: /** * foo - function foo * @arg

Re: [Intel-gfx] USB-C DP mode problem on linux

2020-11-16 Thread Andrzej Kre
Hi, Sure. Ticket #2683 https://gitlab.freedesktop.org/drm/intel/-/issues/2683 Best regards, sob., 14 lis 2020 o 21:11 Saarinen, Jani napisał(a): > Hi, > What is exact gitlab issue for this, can you send link? > > > -Original Message- > > From: Intel-gfx On Behalf Of > Andrzej Kre > >

Re: [Intel-gfx] [RFC i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Tvrtko Ursulin
On 16/11/2020 14:03, Zbigniew Kempczyński wrote: On Fri, Nov 13, 2020 at 04:27:34PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin After devices are sorted post scanning, assing a card index to each so it can be easily accessed if PCI filter for a card needs to be printed out. Signed-off-

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix wrong return value of perf_series_engines()

2020-11-16 Thread Mika Kuoppala
Zhang Xiaoxu writes: > If intel context create failed, the perf_series_engines() will return 0 > rather than error, because we doesn't initialize the return value. > > Fixes: cbfd3a0c5a55 ("drm/i915/selftests: Add request throughput measurement > to perf") > Reported-by: Hulk Robot > Signed-off

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gt: Track the overall busy time (rev2)

2020-11-16 Thread Patchwork
== Series Details == Series: drm/i915/gt: Track the overall busy time (rev2) URL : https://patchwork.freedesktop.org/series/83883/ State : failure == Summary == CI Bug Log - changes from CI_DRM_9337 -> Patchwork_18912 Summary --- **F

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix wrong return value of perf_request_latency()

2020-11-16 Thread Mika Kuoppala
Zhang Xiaoxu writes: > If intel context create failed, the perf_request_latency() will return 0 > rather than error, because we doesn't initialize the return value. > > Fixes: 25c26f18ea79 ("drm/i915/selftests: Measure dispatch latency") > Reported-by: Hulk Robot > Signed-off-by: Zhang Xiaoxu

Re: [Intel-gfx] [PXP CLEAN PATCH v06 02/27] drm/i915/pxp: Enable PXP irq worker and callback stub

2020-11-16 Thread Souza, Jose
On Fri, 2020-11-13 at 16:36 -0800, Sean Z Huang wrote: > From: "Huang, Sean Z" > > Create the irq worker that serves as callback handler, those > callback stubs should be called while the hardware key teardown > occurs. > > Signed-off-by: Huang, Sean Z > --- >  drivers/gpu/drm/i915/gt/intel_gt_

Re: [Intel-gfx] [PXP CLEAN PATCH v06 01/27] drm/i915/pxp: Introduce Intel PXP component

2020-11-16 Thread Souza, Jose
On Fri, 2020-11-13 at 16:36 -0800, Sean Z Huang wrote: > From: "Huang, Sean Z" > > PXP (Protected Xe Path) is an i915 componment, that > helps ring3 to establish the hardware protected session and > manage the status of each alive software session, as well as > the life cycle of each session. >

Re: [Intel-gfx] [RFC i-g-t 3/5] lib/igt_device_scan: Remember PCI card index after scanning

2020-11-16 Thread Zbigniew Kempczyński
On Fri, Nov 13, 2020 at 04:27:34PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > After devices are sorted post scanning, assing a card index to each so it > can be easily accessed if PCI filter for a card needs to be printed out. > > Signed-off-by: Tvrtko Ursulin > Cc: Petri Latvala

[Intel-gfx] [PATCH] drm/i915/lspcon: enter standby mode to enhance power saving

2020-11-16 Thread Lee Shawn C
After system boot up, LSPCON will be configured as PCON mode. But it never go into power saving state. Source driver can do the following. Then LSPCON can enter standby mode automatically to save more power. 1. At PCON mode, source driver write 0x2 to DPCD 600h. 2. At LS mode, try to disable DP_DU

[Intel-gfx] [PATCH v2] drm/i915/gt: Track the overall busy time

2020-11-16 Thread Chris Wilson
Since we wake the GT up before executing a request, and go to sleep as soon as it is retired, the GT wake time not only represents how long the device is powered up, but also provides a summary, ableit overestimate, of the device runtime. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/i

[Intel-gfx] [PATCH] drm/i915/gt: Track the overall busy time

2020-11-16 Thread Chris Wilson
Since we wake the GT up before executing a request, and go to sleep as soon as it is retired, the GT wake time not only represents how long the device is powered up, but also provides a summary, ableit overestimate, of the device runtime. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/i

Re: [Intel-gfx] [igt-dev] [RFC i-g-t 0/5] User friendly lsgpu/intel_gpu_top device listing

2020-11-16 Thread Tvrtko Ursulin
On 13/11/2020 16:27, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Please see individual path commit messages for details, but essentially I implemented this: $ sudo tools/lsgpu card1 8086:4905drm:/dev/dri/card1 └─renderD129 drm:/dev/dri/renderD129 c

Re: [Intel-gfx] [PATCH v4 05/27] drm: fix some kernel-doc markups

2020-11-16 Thread Jani Nikula
On Mon, 16 Nov 2020, Mauro Carvalho Chehab wrote: > Some identifiers have different names between their prototypes > and the kernel-doc markup. > > Others need to be fixed, as kernel-doc markups should use this format: > identifier - description > > Signed-off-by: Mauro Carvalho Chehab >

Re: [Intel-gfx] [PATCH 06/27] drm/i915: Rename the whitelist to allowlist

2020-11-16 Thread Chris Wilson
Quoting Joonas Lahtinen (2020-11-16 10:26:31) > Quoting Huang, Sean Z (2020-11-15 23:07:54) > > Rename the whitelist to allowlist as suggested > > This patch should really be a separate series and most likely needs to > be done in one go to avoid confusion. > > $ git grep -E '(whitelist|blacklist

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] tools/intel_gpu_top: Show the active device

2020-11-16 Thread Tvrtko Ursulin
On 13/11/2020 13:56, Chris Wilson wrote: Include the active device name on the update screen. Signed-off-by: Chris Wilson --- tools/intel_gpu_top.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c index 298defa4e.

Re: [Intel-gfx] [PATCH 07/27] drm/i915/pxp: Add PXP-related registers into allowlist

2020-11-16 Thread Chris Wilson
Quoting Joonas Lahtinen (2020-11-16 10:33:07) > Quoting Huang, Sean Z (2020-11-15 23:07:55) > > Add several PXP-related reg into allowlist to allow > > ring3 driver to read the those register values. > > The individual registers need to be spelled out and their usage on the > UMD side needs to be

Re: [Intel-gfx] [PATCH 23/27] mei: bus: enable pavp device.

2020-11-16 Thread Joonas Lahtinen
Quoting Winkler, Tomas (2020-11-16 12:49:54) > > > > -Original Message- > > From: Joonas Lahtinen > > Sent: Monday, November 16, 2020 11:47 > > To: Huang, Sean Z ; Intel- > > g...@lists.freedesktop.org > > Cc: Winkler, Tomas > > Subject: Re: [Intel-gfx] [PATCH 23/27] mei: bus: enable pa

Re: [Intel-gfx] [PATCH 10/27] drm/i915/pxp: Enable ioctl action to reserve session slot

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:07:58) > With this ioctl action, ring3 driver can reserve a specific > session slot/id assigned by ring0 PXP, as the first step of PXP > session establishment flow. Ring3 PXP stores the session info in > the session list structure. The whole suggested userspace

Re: [Intel-gfx] [PATCH 20/27] drm/i915/pxp: Create the arbitrary session after boot

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:08:08) > Create the arbitrary session, with the fixed session id 0xf, after > system boot, for the case that application allocates the protected > buffer without establishing any protection session. Because the > hardware requires at least one alive session for

Re: [Intel-gfx] [PATCH 05/27] drm/i915/pxp: Enable ioctl action to set the ring3 context

2020-11-16 Thread Chris Wilson
Quoting Joonas Lahtinen (2020-11-16 10:22:23) > Quoting Huang, Sean Z (2020-11-15 23:07:53) > > Enable one ioctl action to allow ring3 driver to set its ring3 > > context, so ring0 PXP can track the context id through this ring3 > > context list. > > Overall the patches should refer to "userspace"

Re: [Intel-gfx] [PATCH 23/27] mei: bus: enable pavp device.

2020-11-16 Thread Winkler, Tomas
> -Original Message- > From: Joonas Lahtinen > Sent: Monday, November 16, 2020 11:47 > To: Huang, Sean Z ; Intel- > g...@lists.freedesktop.org > Cc: Winkler, Tomas > Subject: Re: [Intel-gfx] [PATCH 23/27] mei: bus: enable pavp device. > > Obviously needs to be reviewed in the right ma

Re: [Intel-gfx] [PATCH 22/27] drm/i915/pxp: Expose session state for display protection flip

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:08:10) > Implement the intel_pxp_gem_object_status() to allow ring0 i915 > display querying the current PXP session state. In the design, > ring0 display should not perform protection flip on the protected > buffers if there is no PXP session alive. No users fo

Re: [Intel-gfx] [PATCH 23/27] mei: bus: enable pavp device.

2020-11-16 Thread Joonas Lahtinen
Obviously needs to be reviewed in the right mailing lists and as there don't seem to be any code dependencies should be merged there too. Regards, Joonas Quoting Huang, Sean Z (2020-11-15 23:08:11) > From: Tomas Winkler > > Enable protected audio video path client on mei client > bus. > > Sign

Re: [Intel-gfx] [PATCH 25/27] drm/i915/uapi: introduce drm_i915_gem_create_ext for TGL

2020-11-16 Thread Joonas Lahtinen
Forgot to mention, the patch title doesn't make sense. Quoting Joonas Lahtinen (2020-11-16 12:38:46) > Quoting Huang, Sean Z (2020-11-15 23:08:13) > > From: Bommu Krishnaiah > > > > Same old gem_create but with now with extensions support. This is needed > > to support various upcoming usecases.

Re: [Intel-gfx] [PATCH 25/27] drm/i915/uapi: introduce drm_i915_gem_create_ext for TGL

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:08:13) > From: Bommu Krishnaiah > > Same old gem_create but with now with extensions support. This is needed > to support various upcoming usecases. For now we use the extensions > mechanism to support PAVP. The uAPI related patches should be self-descriptive

Re: [Intel-gfx] [PATCH 07/27] drm/i915/pxp: Add PXP-related registers into allowlist

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:07:55) > Add several PXP-related reg into allowlist to allow > ring3 driver to read the those register values. The individual registers need to be spelled out and their usage on the UMD side needs to be documented. There needs to be a link to the Open Source u

Re: [Intel-gfx] [PATCH 06/27] drm/i915: Rename the whitelist to allowlist

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:07:54) > Rename the whitelist to allowlist as suggested This patch should really be a separate series and most likely needs to be done in one go to avoid confusion. $ git grep -E '(whitelist|blacklist)' | wc -l 173 The next patch also uses "passlist" terminol

Re: [Intel-gfx] [PATCH 05/27] drm/i915/pxp: Enable ioctl action to set the ring3 context

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:07:53) > Enable one ioctl action to allow ring3 driver to set its ring3 > context, so ring0 PXP can track the context id through this ring3 > context list. Overall the patches should refer to "userspace" not "ring3" to avoid confusion. "kernel" vs "user" not ri

Re: [Intel-gfx] [PATCH 01/27] drm/i915/pxp: Introduce Intel PXP component

2020-11-16 Thread Joonas Lahtinen
Quoting Huang, Sean Z (2020-11-15 23:07:49) > PXP (Protected Xe Path) is an i915 componment, that > helps ring3 to establish the hardware protected session and > manage the status of each alive software session, as well as > the life cycle of each session. > > By design PXP will expose ioctl so al

Re: [Intel-gfx] [PATCH 05/27] drm/i915/pxp: Enable ioctl action to set the ring3 context

2020-11-16 Thread Dan Carpenter
Hi Sean, url: https://github.com/0day-ci/linux/commits/Sean-Z-Huang/drm-i915-pxp-Introduce-Intel-PXP-component/20201114-094926 base:92edc4aef86780a8ad01b092c6d6630bb3cb423d config: i386-randconfig-m021-20201115 (attached as .config) compiler: gcc-9 (Debian 9.3.0-15) 9.3.0 If you fix the i

Re: [Intel-gfx] [drm-tip:drm-tip 1117/1129] drivers/gpu/drm/drm_atomic_uapi.c:342 drm_atomic_set_crtc_for_connector() error: we previously assumed 'crtc' could be null (see line 326)

2020-11-16 Thread Simon Ser
Already fixed in 0003b687ee6d ("drm: fix oops in drm_atomic_set_crtc_for_connector"). Thanks. ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] [drm-tip:drm-tip 1117/1129] drivers/gpu/drm/drm_atomic_uapi.c:342 drm_atomic_set_crtc_for_connector() error: we previously assumed 'crtc' could be null (see line 326)

2020-11-16 Thread Dan Carpenter
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: af383973ac39069d9ffcac0287a896a107005d54 commit: e3aae683e861a987d3d7dca593aaff93ac001bcb [1117/1129] drm: convert drm_atomic_uapi.c to new debug helpers config: i386-randconfig-m021-20201115 (attached as .config) compiler: gcc-9 (D

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,v2,1/3] drm/i915: Precompute can_sagv for each wm level

2020-11-16 Thread Patchwork
== Series Details == Series: series starting with [CI,v2,1/3] drm/i915: Precompute can_sagv for each wm level URL : https://patchwork.freedesktop.org/series/83874/ State : success == Summary == CI Bug Log - changes from CI_DRM_9334 -> Patchwork_18911 ==