[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dp: wait on timeout before retry (rev3)

== Series Details == Series: drm/i915/dp: wait on timeout before retry (rev3) URL : https://patchwork.freedesktop.org/series/105660/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11840_full -> Patchwork_105660v3_full Summar

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr

== Series Details == Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr URL : https://patchwork.freedesktop.org/series/105883/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11842 -> Patchwork_105883v1 Su

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr

== Series Details == Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr URL : https://patchwork.freedesktop.org/series/105883/ State : warning == Summary == Error: dim checkpatch failed 044b58d3ed70 drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr -:135: CHECK

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: switch DP, HDMI and LVDS to drm_edid

== Series Details == Series: drm/i915: switch DP, HDMI and LVDS to drm_edid URL : https://patchwork.freedesktop.org/series/105857/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11840_full -> Patchwork_105857v1_full Summary

Re: [Intel-gfx] [PATCH] drm/i915/display: clean up comments

On Fri, Jul 01, 2022 at 04:32:36PM -0400, Tom Rix wrote: > spelling changes > resoluition -> resolution > dont-> don't > commmit -> commit > Invalidade -> Invalidate > > Signed-off-by: Tom Rix Reviewed-by: Matt Roper and applied to drm-intel-next. Thanks for the patch. Matt >

Re: [Intel-gfx] [PATCH v8 0/3] drm/doc/rfc: i915 VM_BIND feature design + uapi

On Thu, Jun 30, 2022 at 05:31:07PM -0700, Niranjana Vishwanathapura wrote: > This is the i915 driver VM_BIND feature design RFC patch series along > with the required uapi definition and description of intended use cases. > > v2: Reduce the scope to simple Mesa use case. > Remove all compute r

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/vm_bind: Add VM_BIND functionality

== Series Details == Series: drm/i915/vm_bind: Add VM_BIND functionality URL : https://patchwork.freedesktop.org/series/105879/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11841 -> Patchwork_105879v1 Summary --- **

Re: [Intel-gfx] [PATCH 2/2] drm/i915: DG2 and ATS-M device ID updates

On Fri, Jul 01, 2022 at 09:59:50AM -0700, Lucas De Marchi wrote: > On Fri, Jul 01, 2022 at 08:22:31AM -0700, Matt Roper wrote: > > Small BAR support has now landed, which allows us to add the PCI IDs > > that correspond to add-in card designs of DG2 and ATS-M. There's also > > one additional MB-do

[Intel-gfx] [PATCH] drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr

Although all DSS belong to a single pool on Xe_HP platforms (i.e., they're not organized into slices from a topology point of view), we do still need to pass 'group' and 'instance' targets when steering register accesses to a specific instance of a per-DSS multicast register. The rules for how to

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/vm_bind: Add VM_BIND functionality

== Series Details == Series: drm/i915/vm_bind: Add VM_BIND functionality URL : https://patchwork.freedesktop.org/series/105879/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/vm_bind: Add VM_BIND functionality

== Series Details == Series: drm/i915/vm_bind: Add VM_BIND functionality URL : https://patchwork.freedesktop.org/series/105879/ State : warning == Summary == Error: dim checkpatch failed 9a618f815c5e drm/i915/vm_bind: Introduce VM_BIND ioctl -:196: WARNING:LONG_LINE: line length of 118 exceeds

[Intel-gfx] [RFC 07/10] drm/i915/vm_bind: Handle persistent vmas in execbuf3

Handle persistent (VM_BIND) mappings during the request submission in the execbuf3 path. Signed-off-by: Niranjana Vishwanathapura --- .../gpu/drm/i915/gem/i915_gem_execbuffer3.c | 176 +- 1 file changed, 175 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gem/i9

[Intel-gfx] [RFC 05/10] drm/i915/vm_bind: Handle persistent vmas

Treat VM_BIND vmas as persistent and handle them during the request submission in the execbuff path. Support eviction by maintaining a list of evicted persistent vmas for rebinding during next submission. Signed-off-by: Niranjana Vishwanathapura --- drivers/gpu/drm/i915/gem/i915_gem_object.c

[Intel-gfx] [RFC 04/10] drm/i915/vm_bind: Add out fence support

Add support for handling out fence of vm_bind call. Signed-off-by: Niranjana Vishwanathapura --- drivers/gpu/drm/i915/gem/i915_gem_vm_bind.h | 2 + .../drm/i915/gem/i915_gem_vm_bind_object.c| 74 +++ drivers/gpu/drm/i915/i915_vma.c | 6 +- drivers/gpu/drm/i9

[Intel-gfx] [RFC 08/10] drm/i915/vm_bind: userptr dma-resv changes

For persistent (vm_bind) vmas of userptr BOs, handle the user page pinning by using the i915_gem_object_userptr_submit_init() /done() functions Signed-off-by: Niranjana Vishwanathapura --- .../gpu/drm/i915/gem/i915_gem_execbuffer3.c | 67 +++ .../drm/i915/gem/i915_gem_vm_bind_o

[Intel-gfx] [RFC 02/10] drm/i915/vm_bind: Bind and unbind mappings

Bind and unbind the mappings upon VM_BIND and VM_UNBIND calls. Signed-off-by: Niranjana Vishwanathapura Signed-off-by: Prathap Kumar Valsan --- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/gem/i915_gem_create.c| 10 +- drivers/gpu/drm/i915/gem/i915_gem_object

[Intel-gfx] [RFC 10/10] drm/i915/vm_bind: Fix vm->vm_bind_mutex and vm->mutex nesting

VM_BIND functionality maintain that vm->vm_bind_mutex will never be taken while holding vm->mutex. However, while closing 'vm', vma is destroyed while holding vm->mutex. But vma releasing needs to take vm->vm_bind_mutex in order to delete vma from the vm_bind_list. To avoid this, destroy the vma ou

[Intel-gfx] [RFC 03/10] drm/i915/vm_bind: Support private and shared BOs

Add uapi allowing user to specify a BO as private to a specified VM during the BO creation. VM private BOs can only be mapped on the specified VM and can't be dma_buf exported. VM private BOs share a single common dma_resv object, hence has a performance advantage requiring a single dma_resv object

[Intel-gfx] [RFC 09/10] drm/i915/vm_bind: Skip vma_lookup for persistent vmas

vma_lookup is tied to segment of the object instead of section of VA space. Hence, it do not support aliasing (ie., multiple bindings to the same section of the object). Skip vma_lookup for persistent vmas as it supports aliasing. Signed-off-by: Niranjana Vishwanathapura --- drivers/gpu/drm/i915

[Intel-gfx] [RFC 06/10] drm/i915/vm_bind: Add I915_GEM_EXECBUFFER3 ioctl

Add new execbuf3 ioctl (I915_GEM_EXECBUFFER3) which only works in vm_bind mode. The vm_bind mode only works with this new execbuf3 ioctl. The new execbuf3 ioctl will not have any execlist support and all the legacy support like relocations etc are removed. Signed-off-by: Niranjana Vishwanathapura

[Intel-gfx] [RFC 01/10] drm/i915/vm_bind: Introduce VM_BIND ioctl

Add VM_BIND and VM_UNBIND ioctls to bind/unbind a section of an object at the specified GPU virtual addresses. Add I915_PARAM_VM_BIND_VERSION to indicate version of VM_BIND feature supported and I915_VM_CREATE_FLAGS_USE_VM_BIND for UMDs to select the vm_bind mode of binding. Signed-off-by: Niranj

[Intel-gfx] [RFC 00/10] drm/i915/vm_bind: Add VM_BIND functionality

DRM_I915_GEM_VM_BIND/UNBIND ioctls allows UMD to bind/unbind GEM buffer objects (BOs) or sections of a BOs at specified GPU virtual addresses on a specified address space (VM). Multiple mappings can map to the same physical pages of an object (aliasing). These mappings (also referred to as persiste

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display: clean up comments

== Series Details == Series: drm/i915/display: clean up comments URL : https://patchwork.freedesktop.org/series/105877/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11841 -> Patchwork_105877v1 Summary --- **FAILURE*

[Intel-gfx] [PATCH] drm/i915/display: clean up comments

spelling changes resoluition -> resolution dont-> don't commmit -> commit Invalidade -> Invalidate Signed-off-by: Tom Rix --- drivers/gpu/drm/i915/display/intel_psr.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/i915/display/intel_psr.c

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/doc/rfc: i915 VM_BIND feature design + uapi

== Series Details == Series: drm/doc/rfc: i915 VM_BIND feature design + uapi URL : https://patchwork.freedesktop.org/series/105845/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11837_full -> Patchwork_105845v1_full Summary

Re: [Intel-gfx] [PATCH] drm/i915: Fix NPD in PMU during driver teardown

On Fri, Jul 01, 2022 at 09:37:20AM +0100, Tvrtko Ursulin wrote: On 01/07/2022 01:11, Umesh Nerlige Ramappa wrote: On Thu, Jun 30, 2022 at 09:00:28PM +, Stuart Summers wrote: In the driver teardown, we are unregistering the gt prior to unregistering the PMU. This means there is a small wind

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix NPD in PMU during driver teardown (rev4)

== Series Details == Series: drm/i915: Fix NPD in PMU during driver teardown (rev4) URL : https://patchwork.freedesktop.org/series/105790/ State : success == Summary == CI Bug Log - changes from CI_DRM_11841 -> Patchwork_105790v4 Summary --

Re: [Intel-gfx] [PATCH 1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

On Fri, Jul 01, 2022 at 08:22:30AM -0700, Matt Roper wrote: This reverts commit f7d7dddaab81eeae4508197b5f38f0b974d97b8c. In reality we'll just rebase this patch out of the topic/core-for-CI branch after landing the "real" copy in drm-intel. But to prevent pre-merge CI from getting confused, we

Re: [Intel-gfx] [PATCH 2/2] drm/i915: DG2 and ATS-M device ID updates

On Fri, Jul 01, 2022 at 08:22:31AM -0700, Matt Roper wrote: Small BAR support has now landed, which allows us to add the PCI IDs that correspond to add-in card designs of DG2 and ATS-M. There's also one additional MB-down PCI ID that recently appeared (0x5698) so we add it too. Cc: Lucas De Mar

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix NPD in PMU during driver teardown (rev3)

== Series Details == Series: drm/i915: Fix NPD in PMU during driver teardown (rev3) URL : https://patchwork.freedesktop.org/series/105790/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11836_full -> Patchwork_105790v3_full

[Intel-gfx] [PATCH] drm/i915: Fix NPD in PMU during driver teardown

In the driver teardown, we are unregistering the gt prior to unregistering the PMU. This means there is a small window of time in which the application can request metrics from the PMU, some of which are calling into the uapi engines list, while the engines are not available. In this case we can se

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

== Series Details == Series: series starting with [1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs" URL : https://patchwork.freedesktop.org/series/105870/ State : success == Summary == CI Bug Log - changes from CI_DRM_11840 -> Patchwork_105870v1

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Implement w/a 16016694945

On Fri, Jul 01, 2022 at 12:52:21PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/pvc: Implement w/a 16016694945 > URL : https://patchwork.freedesktop.org/series/105837/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11835_full -> Patchwork_105837

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

== Series Details == Series: series starting with [1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs" URL : https://patchwork.freedesktop.org/series/105870/ State : warning == Summary == Error: dim checkpatch failed 4863bd4151f5 Revert "topic/core-for-CI: Add remaining DG

[Intel-gfx] [PATCH 1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

This reverts commit f7d7dddaab81eeae4508197b5f38f0b974d97b8c. In reality we'll just rebase this patch out of the topic/core-for-CI branch after landing the "real" copy in drm-intel. But to prevent pre-merge CI from getting confused, we send it as an explicit revert on the mailing list. Cc: Lucas

[Intel-gfx] [PATCH 2/2] drm/i915: DG2 and ATS-M device ID updates

Small BAR support has now landed, which allows us to add the PCI IDs that correspond to add-in card designs of DG2 and ATS-M. There's also one additional MB-down PCI ID that recently appeared (0x5698) so we add it too. Cc: Lucas De Marchi Signed-off-by: Matt Roper --- drivers/gpu/drm/i915/i915

Re: [Intel-gfx] [PATCH] drm/i915: Fix NPD in PMU during driver teardown

On Fri, 2022-07-01 at 09:37 +0100, Tvrtko Ursulin wrote: > On 01/07/2022 01:11, Umesh Nerlige Ramappa wrote: > > On Thu, Jun 30, 2022 at 09:00:28PM +, Stuart Summers wrote: > > > In the driver teardown, we are unregistering the gt prior > > > to unregistering the PMU. This means there is a smal

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix NPD in PMU during driver teardown (rev2)

== Series Details == Series: drm/i915: Fix NPD in PMU during driver teardown (rev2) URL : https://patchwork.freedesktop.org/series/105790/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11835_full -> Patchwork_105790v2_full

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Nuke PCH_MCC

On Fri, 01 Jul 2022, Ville Syrjälä wrote: > On Fri, Jul 01, 2022 at 12:55:43PM +0300, Jani Nikula wrote: >> On Thu, 30 Jun 2022, Ville Syrjala wrote: >> > From: Ville Syrjälä >> > >> > MCC is derived from TGP, and we have no real need to >> > differentiate between the two. Thus remove PCH_MCC an

Re: [Intel-gfx] [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

On Fri, Jul 01, 2022 at 11:55:38AM +0300, Jani Nikula wrote: > Convert all the connectors that use cached connector edid and > detect_edid to drm_edid. > > Since drm_get_edid() calls drm_connector_update_edid_property() while > drm_edid_read*() do not, we need to call drm_edid_connector_update() >

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Implement w/a 16016694945

== Series Details == Series: drm/i915/pvc: Implement w/a 16016694945 URL : https://patchwork.freedesktop.org/series/105837/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11835_full -> Patchwork_105837v1_full Summary ---

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Nuke PCH_MCC

On Fri, Jul 01, 2022 at 12:55:43PM +0300, Jani Nikula wrote: > On Thu, 30 Jun 2022, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > MCC is derived from TGP, and we have no real need to > > differentiate between the two. Thus remove PCH_MCC and > > just declare it to be PCH_TGP compatible. >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: wait on timeout before retry (rev3)

== Series Details == Series: drm/i915/dp: wait on timeout before retry (rev3) URL : https://patchwork.freedesktop.org/series/105660/ State : success == Summary == CI Bug Log - changes from CI_DRM_11840 -> Patchwork_105660v3 Summary ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm: Clean up drm_crtc.h (rev6)

== Series Details == Series: drm: Clean up drm_crtc.h (rev6) URL : https://patchwork.freedesktop.org/series/105073/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11835_full -> Patchwork_105073v6_full Summary --- **FA

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dp: wait on timeout before retry (rev2)

== Series Details == Series: drm/i915/dp: wait on timeout before retry (rev2) URL : https://patchwork.freedesktop.org/series/105660/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11840 -> Patchwork_105660v2 Summary ---

Re: [Intel-gfx] [PATCHv3] drm/i915/dp: wait on timeout before retry

On Fri, 01 Jul 2022, Arun R Murthy wrote: > On linktraining error/timeout before retry need to wait for 400usec as > per the DP CTS spec1.2 > > The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in Displayport > AUX transactions for compliance testing") > removes this delay mentioning the

[Intel-gfx] [PATCHv3] drm/i915/dp: wait on timeout before retry

On linktraining error/timeout before retry need to wait for 400usec as per the DP CTS spec1.2 The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in Displayport AUX transactions for compliance testing") removes this delay mentioning the hardware already meets this requirement, but as per th

Re: [Intel-gfx] [PATCHv2] drm/i915/dp: wait on timeout before retry

On Fri, 01 Jul 2022, Arun R Murthy wrote: > On linktraining error/timeout before retry need to wait for 400usec as > per the DP CTS spec1.2 > > The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in Displayport > AUX transactions for compliance testing") > removes this delay mentioning the

[Intel-gfx] [PATCHv2] drm/i915/dp: wait on timeout before retry

On linktraining error/timeout before retry need to wait for 400usec as per the DP CTS spec1.2 The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in Displayport AUX transactions for compliance testing") removes this delay mentioning the hardware already meets this requirement, but as per th

Re: [Intel-gfx] [PATCH v6] drm/i915/dsi: add payload receiving code

On Wed, 22 Jun 2022, William Tseng wrote: > To support Host to read data from Peripheral after > a DCS read command is sent over DSI. Please find a couple of comments inline below. Basically with them fixed this is Acked-by: Jani Nikula I'm afraid I just don't have the time for further detaile

Re: [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry

> On Mon, 27 Jun 2022, Arun R Murthy wrote: > > On linktraining error/timeout before retry need to wait for 400usec as > > per the DP CTS spec1.2 The patch with commit id > > 74ebf294a1dd816bdc248ac733009a8915d59eb5 > > drm/i915: Add a delay in Displayport AUX transactions for compliance > > testi

Re: [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry

On Mon, 27 Jun 2022, Arun R Murthy wrote: > On linktraining error/timeout before retry need to wait for 400usec as > per the DP CTS spec1.2 > The patch with commit id > 74ebf294a1dd816bdc248ac733009a8915d59eb5 > drm/i915: Add a delay in Displayport AUX transactions for > compliance testing Please

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: switch DP, HDMI and LVDS to drm_edid

== Series Details == Series: drm/i915: switch DP, HDMI and LVDS to drm_edid URL : https://patchwork.freedesktop.org/series/105857/ State : success == Summary == CI Bug Log - changes from CI_DRM_11840 -> Patchwork_105857v1 Summary ---

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Nuke PCH_JSP

On Thu, 30 Jun 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > JSP is based on ICP and we don't really need to differentiate > between the two. So let's just delcare JSP to be ICP. > > The only slight change here is for Wa_14011294188 which we > used to apply for JSP but now we'll only apply

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Nuke PCH_MCC

On Thu, 30 Jun 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > MCC is derived from TGP, and we have no real need to > differentiate between the two. Thus remove PCH_MCC and > just declare it to be PCH_TGP compatible. > > Signed-off-by: Ville Syrjälä > --- > drivers/gpu/drm/i915/display/int

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Use short PCH names consistently

On Thu, 30 Jun 2022, Ville Syrjälä wrote: > On Thu, Jun 30, 2022 at 03:50:15PM +, Murthy, Arun R wrote: >> > From: Ville Syrjälä >> > >> > The comments regarding PCH compatibility use long vs. >> > short names inconsistently. Just use short names always. >> > >> > Signed-off-by: Ville Syrjä

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: PCH type cleanup

== Series Details == Series: drm/i915: PCH type cleanup URL : https://patchwork.freedesktop.org/series/105822/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11834_full -> Patchwork_105822v1_full Summary --- **FAILURE

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: switch DP, HDMI and LVDS to drm_edid

== Series Details == Series: drm/i915: switch DP, HDMI and LVDS to drm_edid URL : https://patchwork.freedesktop.org/series/105857/ State : warning == Summary == Error: dim checkpatch failed 4db4abe80683 drm/i915/edid: convert DP, HDMI and LVDS to drm_edid -:281: CHECK:COMPARISON_TO_NULL: Compa

Re: [Intel-gfx] [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

On Fri, 01 Jul 2022, Jani Nikula wrote: > Convert all the connectors that use cached connector edid and > detect_edid to drm_edid. > > Since drm_get_edid() calls drm_connector_update_edid_property() while > drm_edid_read*() do not, we need to call drm_edid_connector_update() > separately, in part

[Intel-gfx] [PATCH v4 2/2] drm/i915/bios: convert intel_bios_init_panel() to drm_edid

Try to use struct drm_edid where possible, even if having to fall back to looking into struct edid down low via drm_edid_raw(). v2: Rebase Signed-off-by: Jani Nikula Reviewed-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_bios.c | 19 ++- drivers/gpu/drm/i915/display/

[Intel-gfx] [PATCH v4 0/2] drm/i915: switch DP, HDMI and LVDS to drm_edid

The remaining patches to add HF-EEODB support to i915 by switching to using drm_edid in certain encoders. This depends on the drm_edid work in drm-misc-next, and either needs to be merged via drm-misc-next, or we'll need the dependencies merged to drm-intel-next via drm-misc-next pull request -> dr

[Intel-gfx] [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

Convert all the connectors that use cached connector edid and detect_edid to drm_edid. Since drm_get_edid() calls drm_connector_update_edid_property() while drm_edid_read*() do not, we need to call drm_edid_connector_update() separately, in part due to the EDID caching behaviour in HDMI and DP. Es

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: stop HPD workers before display driver unregister (rev2)

== Series Details == Series: drm/i915/display: stop HPD workers before display driver unregister (rev2) URL : https://patchwork.freedesktop.org/series/105557/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11834_full -> Patchwork_105557v2_full =

Re: [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition

On 30/06/2022 17:23, Matthew Auld wrote: On 30/06/2022 16:34, Jason Ekstrand wrote: On Thu, Jun 30, 2022 at 10:14 AM Matthew Auld > wrote:     On 30/06/2022 06:11, Jason Ekstrand wrote: > On Sat, Jun 25, 2022 at 8:49 PM Niranjana Vishwanathapura > mailto

Re: [Intel-gfx] [PATCH] drm/i915: Fix NPD in PMU during driver teardown

On 01/07/2022 01:11, Umesh Nerlige Ramappa wrote: On Thu, Jun 30, 2022 at 09:00:28PM +, Stuart Summers wrote: In the driver teardown, we are unregistering the gt prior to unregistering the PMU. This means there is a small window of time in which the application can request metrics from the

Re: [Intel-gfx] [PATCH v2] drm/i915: Fix vm use-after-free in vma destruction

On Mon, 20 Jun 2022 at 13:37, Thomas Hellström wrote: > > In vma destruction, the following race may occur: > > Thread 1: Thread 2: > i915_vma_destroy(); > > ... > list_del_init(vma->vm_link); > ... > mutex_unlock(vma->vm->mutex); >

Re: [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition

On 30/06/2022 17:22, Niranjana Vishwanathapura wrote: On Thu, Jun 30, 2022 at 08:59:09AM +0100, Tvrtko Ursulin wrote: On 30/06/2022 07:08, Niranjana Vishwanathapura wrote: On Wed, Jun 29, 2022 at 05:33:49PM -0700, Zanoni, Paulo R wrote: On Sat, 2022-06-25 at 18:49 -0700, Niranjana Vishwanat

Re: [Intel-gfx] [PATCH 5/6] drm/i915/gt: Serialize GRDOM access between multiple engine resets

On 30/06/2022 17:01, Mauro Carvalho Chehab wrote: Em Thu, 30 Jun 2022 09:12:41 +0100 Tvrtko Ursulin escreveu: On 30/06/2022 08:32, Mauro Carvalho Chehab wrote: Em Wed, 29 Jun 2022 17:02:59 +0100 Tvrtko Ursulin escreveu: On 29/06/2022 16:30, Mauro Carvalho Chehab wrote: On Tue, 28 Jun

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Remove flush_scheduled_work() from live_execlists

== Series Details == Series: drm/i915/selftests: Remove flush_scheduled_work() from live_execlists URL : https://patchwork.freedesktop.org/series/105816/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11834_full -> Patchwork_105816v1_full ===

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: ttm for stolen (rev5)

On 30/06/2022 15:20, Robert Beckett wrote: On 29/06/2022 13:51, Robert Beckett wrote: On 28/06/2022 17:22, Robert Beckett wrote: On 28/06/2022 09:46, Tvrtko Ursulin wrote: On 27/06/2022 18:08, Robert Beckett wrote: On 22/06/2022 10:05, Tvrtko Ursulin wrote: On 21/06/2022 20:11, R