[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: pps_lock moved to encoder to support dual EDP

== Series Details == Series: drm/i915: pps_lock moved to encoder to support dual EDP URL : https://patchwork.freedesktop.org/series/98221/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11014 -> Patchwork_21877 Summary -

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: pps_lock moved to encoder to support dual EDP

== Series Details == Series: drm/i915: pps_lock moved to encoder to support dual EDP URL : https://patchwork.freedesktop.org/series/98221/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] [PATCH] drm/i915: pps_lock moved to encoder to support dual EDP

Currently dev_priv->pps_lock is used for locking mechanism and one instance of pps registers are used for pps register programming. Second instance enabled as per port number and pps_lock is moved under encoder. Signed-off-by: Animesh Manna --- .../drm/i915/display/intel_display_types.h| 3

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for More preparation for multi gt patches

Regressions are related to https://gitlab.freedesktop.org/drm/intel/-/issues/2842 igt@gem_exec_fair@.* - fail - Failed assertion: iqr[nchild / 2] < result[nchild / 2], Child frame IQR .*ms exceeded median threshold .*m s https://gitlab.freedesktop.org/drm/intel/-/issues/4817 igt@i915_suspend@sys

[Intel-gfx] ✓ Fi.CI.IGT: success for More preparation for multi gt patches

== Series Details == Series: More preparation for multi gt patches URL : https://patchwork.freedesktop.org/series/98215/ State : success == Summary == CI Bug Log - changes from CI_DRM_11014_full -> Patchwork_21876_full Summary --- **

[Intel-gfx] ✓ Fi.CI.BAT: success for More preparation for multi gt patches

== Series Details == Series: More preparation for multi gt patches URL : https://patchwork.freedesktop.org/series/98215/ State : success == Summary == CI Bug Log - changes from CI_DRM_11014 -> Patchwork_21876 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for More preparation for multi gt patches

== Series Details == Series: More preparation for multi gt patches URL : https://patchwork.freedesktop.org/series/98215/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More preparation for multi gt patches

== Series Details == Series: More preparation for multi gt patches URL : https://patchwork.freedesktop.org/series/98215/ State : warning == Summary == $ dim checkpatch origin/drm-tip 99fedc5dc623 drm/i915/gt: Use to_gt() helper for GGTT accesses 3c62ac9c17e8 drm/i915: Use to_gt() helper for GG

[Intel-gfx] [PATCH v9 6/6] drm/i915: Remove unused i915->ggtt

The reference to the GGTT from the private date is not used anymore. Remove it. The ggtt in the root gt will now be dynamically allocated and the deallocation handled by the drmm_* managed allocation. Suggested-by: Matt Roper Signed-off-by: Andi Shyti Cc: Michał Winiarski Reviewed-by: Sujarith

[Intel-gfx] [PATCH v9 5/6] drm/i915/selftests: Use to_gt() helper for GGTT accesses

From: Michał Winiarski GGTT is currently available both through i915->ggtt and gt->ggtt, and we eventually want to get rid of the i915->ggtt one. Use to_gt() for all i915->ggtt accesses to help with the future refactoring. Signed-off-by: Michał Winiarski Cc: Michal Wajdeczko Signed-off-by: And

[Intel-gfx] [PATCH v9 2/6] drm/i915: Use to_gt() helper for GGTT accesses

From: Michał Winiarski GGTT is currently available both through i915->ggtt and gt->ggtt, and we eventually want to get rid of the i915->ggtt one. Use to_gt() for all i915->ggtt accesses to help with the future refactoring. Signed-off-by: Michał Winiarski Cc: Michal Wajdeczko Signed-off-by: And

[Intel-gfx] [PATCH v9 4/6] drm/i915/display: Use to_gt() helper for GGTT accesses

From: Michał Winiarski GGTT is currently available both through i915->ggtt and gt->ggtt, and we eventually want to get rid of the i915->ggtt one. Use to_gt() for all i915->ggtt accesses to help with the future refactoring. Signed-off-by: Michał Winiarski Cc: Michal Wajdeczko Signed-off-by: And

[Intel-gfx] [PATCH v9 3/6] drm/i915/gem: Use to_gt() helper for GGTT accesses

From: Michał Winiarski GGTT is currently available both through i915->ggtt and gt->ggtt, and we eventually want to get rid of the i915->ggtt one. Use to_gt() for all i915->ggtt accesses to help with the future refactoring. Signed-off-by: Michał Winiarski Cc: Michal Wajdeczko Signed-off-by: And

[Intel-gfx] [PATCH v9 1/6] drm/i915/gt: Use to_gt() helper for GGTT accesses

From: Michał Winiarski GGTT is currently available both through i915->ggtt and gt->ggtt, and we eventually want to get rid of the i915->ggtt one. Use to_gt() for all i915->ggtt accesses to help with the future refactoring. Signed-off-by: Michał Winiarski Cc: Michal Wajdeczko Signed-off-by: And

[Intel-gfx] [PATCH v9 0/6] More preparation for multi gt patches

Hi, thanks Matt for merging the first 10 patches from v8. This series contains only the last 6 patches from the previous that make use of the newly inserted to_gt() to reach the ggtt that at the end moves from the i915 structure to the gt. I have reshuffled a bit the order of the patche (refer to

[Intel-gfx] [intel-gfx] How to determine supported HDMI versions of an Intel GPU

[ Please CC me I am not subscribed to any CCed mailing-lists ] Hi Daniel, I hope you are well. While searching for a new monitor I wanted to buy a miniHDMI->HDMI adapter or cable to connect it. My Samsung laptop has a Intel HD graphics 3000 GPU and a miniHDMI connector. Unfortunately, I have n

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix possible uninitialized variable in parallel extension

== Series Details == Series: drm/i915: Fix possible uninitialized variable in parallel extension URL : https://patchwork.freedesktop.org/series/98207/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11014 -> Patchwork_21875 S

Re: [Intel-gfx] [PATCH V3] drm/i915/adl-n: Enable ADL-N platform

On Fri, Dec 17, 2021 at 03:27:57PM +0200, Jani Nikula wrote: On Fri, 10 Dec 2021, Tejas Upadhyay wrote: Adding PCI device ids and enabling ADL-N platform. ADL-N from i915 point of view is subplatform of ADL-P. BSpec: 68397 Changes since V2: - Added version log history Changes since V

Re: [Intel-gfx] [PATCH] drm/i915: Fix possible uninitialized variable in parallel extension

On Sat, Dec 18, 2021 at 04:19:09PM -0800, Matthew Brost wrote: 'prev_engine' was declared inside the output loop and checked in the inner after at least 1 pass of either loop. The variable should be declared outside both loops as it needs to be persistent across the entire loop structure. Fixes: