RE: ✗ Fi.CI.IGT: failure for ALSA: hda/hdmi: add force-connect quirk for ASUSTeK Z170M Pro

Hi, > -Original Message- > From: Intel-gfx On Behalf Of > Patchwork > Sent: Friday, December 8, 2023 9:58 AM > To: Kai Vehmanen > Cc: intel-gfx@lists.freedesktop.org > Subject: ✗ Fi.CI.IGT: failure for ALSA: hda/hdmi: add force-connect quirk for > ASUSTeK Z170M Pro > > Patch Details > Se

✗ Fi.CI.IGT: failure for drm/i915: Fix remapped stride with CCS on ADL+ (rev2)

== Series Details == Series: drm/i915: Fix remapped stride with CCS on ADL+ (rev2) URL : https://patchwork.freedesktop.org/series/127375/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13995_full -> Patchwork_127375v2_full S

Re: [Intel-gfx] â Fi.CI.BAT: failure for drm/i915/display: Check GGTT to determine phys_base (rev2)

On 07.12.2023 12:26, Andrzej Hajda wrote: On 07.12.2023 11:10, Andrzej Hajda wrote: On 07.12.2023 01:18, Patchwork wrote: *Patch Details* *Series:*    drm/i915/display: Check GGTT to determine phys_base (rev2) *URL:*    https://patchwork.freedesktop.org/series/127130/

✗ Fi.CI.SPARSE: warning for Enable Adaptive Sync SDP Support for DP (rev2)

== Series Details == Series: Enable Adaptive Sync SDP Support for DP (rev2) URL : https://patchwork.freedesktop.org/series/126829/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.BAT: failure for Enable Adaptive Sync SDP Support for DP (rev2)

== Series Details == Series: Enable Adaptive Sync SDP Support for DP (rev2) URL : https://patchwork.freedesktop.org/series/126829/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13997 -> Patchwork_126829v2 Summary ---

Re: [PATCH 0/8] drm/i915: Drop pointless null checks and fix a scaler bug

On Thu, 07 Dec 2023, Ville Syrjala wrote: > From: Ville Syrjälä > > Mostly just dropping a bunch of redundant null checks that I ran > into while playing around with __attribute__((nonnull)). > > And I also ended up discovering an actual bug in the scaler code. Series is Reviewed-by: Jani Nikul

✗ Fi.CI.IGT: failure for drm/i915: Drop pointless null checks and fix a scaler bug

== Series Details == Series: drm/i915: Drop pointless null checks and fix a scaler bug URL : https://patchwork.freedesktop.org/series/127525/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13995_full -> Patchwork_127525v1_full ===

Re: [Intel-gfx] [drm-intel:drm-intel-gt-next] [drm/i915] [confidence: ] 9bb66c179f: assertion_failure

On Thu, 07 Dec 2023, kernel test robot wrote: > Hello, > > kernel test robot noticed "assertion_failure" on: > > commit: 9bb66c179f50e61df20ba13c9b34ca17d00b05fb ("drm/i915: Reserve some > kernel space per vm") > git://anongit.freedesktop.org/drm-intel drm-intel-gt-next > > in testcase: igt So t

✓ Fi.CI.IGT: success for Cleanup C20 pll state

== Series Details == Series: Cleanup C20 pll state URL : https://patchwork.freedesktop.org/series/127530/ State : success == Summary == CI Bug Log - changes from CI_DRM_13995_full -> Patchwork_127530v1_full Summary --- **SUCCESS**

RE: ✗ Fi.CI.IGT: failure for ALSA: hda/hdmi: add force-connect quirk for ASUSTeK Z170M Pro

Hi, On Fri, 8 Dec 2023, Saarinen, Jani wrote: > > -Original Message- > > From: Intel-gfx On Behalf Of > > Patchwork > > Sent: Friday, December 8, 2023 9:58 AM > > To: Kai Vehmanen > > Cc: intel-gfx@lists.freedesktop.org > > Subject: ✗ Fi.CI.IGT: failure for ALSA: hda/hdmi: add force-co

[PATCH] drm/i915: fix display ver 12-13 fault error handling

Unless I'm completely misreading the bspec, there are no defined bits for plane gtt fault errors in DE PIPE IIR for a display versions 12-14. This would explain why DG2 in the linked bug is getting thousands of fault errors. Bspec: 50335 Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/97

Re: [PATCH] drm/i915: fix display ver 12-13 fault error handling

On Fri, 08 Dec 2023, Jani Nikula wrote: > Unless I'm completely misreading the bspec, there are no defined bits > for plane gtt fault errors in DE PIPE IIR for a display versions > 12-14. This would explain why DG2 in the linked bug is getting thousands > of fault errors. > > Bspec: 50335 > Closes

RE: [PATCH 1/3] drm/i915/mtl: Use port clock compatible numbers for C20 phy

> -Original Message- > From: Sripada, Radhakrishna > Sent: Friday, December 8, 2023 12:10 AM > To: intel-gfx@lists.freedesktop.org > Cc: Sripada, Radhakrishna ; Taylor, Clinton A > ; Kahola, Mika > > Subject: [PATCH 1/3] drm/i915/mtl: Use port clock compatible numbers for C20 > phy > >

RE: [PATCH 2/3] drm/i915/mtl: Remove misleading "clock" field from C20 pll_state

> -Original Message- > From: Sripada, Radhakrishna > Sent: Friday, December 8, 2023 12:10 AM > To: intel-gfx@lists.freedesktop.org > Cc: Sripada, Radhakrishna ; Taylor, Clinton A > ; Kahola, Mika > > Subject: [PATCH 2/3] drm/i915/mtl: Remove misleading "clock" field from C20 > pll_state

RE: [PATCH 3/3] drm/i915/mtl: Rename the link_bit_rate to clock in C20 pll_state

> -Original Message- > From: Sripada, Radhakrishna > Sent: Friday, December 8, 2023 12:10 AM > To: intel-gfx@lists.freedesktop.org > Cc: Sripada, Radhakrishna ; Taylor, Clinton A > ; Kahola, Mika > > Subject: [PATCH 3/3] drm/i915/mtl: Rename the link_bit_rate to clock in C20 > pll_state

✓ Fi.CI.BAT: success for drm/i915/hdcp: Fail Repeater authentication if Type1 device not present (rev2)

== Series Details == Series: drm/i915/hdcp: Fail Repeater authentication if Type1 device not present (rev2) URL : https://patchwork.freedesktop.org/series/127414/ State : success == Summary == CI Bug Log - changes from CI_DRM_13990 -> Patchwork_127414v2 ===

✓ Fi.CI.IGT: success for drm/i915/display: Add intel_fb_bo_framebuffer_fini

== Series Details == Series: drm/i915/display: Add intel_fb_bo_framebuffer_fini URL : https://patchwork.freedesktop.org/series/127482/ State : success == Summary == CI Bug Log - changes from CI_DRM_13991_full -> Patchwork_127482v1_full Summ

[PATCH] drm/crtc: fix uninitialized variable use

Commit 3823119b9c2b ("drm/crtc: Fix uninit-value bug in drm_mode_setcrtc") was supposed to fix use of an uninitialized variable, but introduced another. num_connectors is only initialized if crtc_req->count_connectors > 0, but it's used regardless. Fix it. Fixes: 3823119b9c2b ("drm/crtc: Fix unin

✗ Fi.CI.BAT: failure for drm/i915: fix display ver 12-13 fault error handling

== Series Details == Series: drm/i915: fix display ver 12-13 fault error handling URL : https://patchwork.freedesktop.org/series/127564/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13999 -> Patchwork_127564v1 Summary

[PATCH 2/2] drm/i915/display: Print PICA version

The PICA_DEVICE_ID follows the same format as other GMD_ID registers (graphics, display and media). Currently the only use for it is informational for developers while checking the differences between machines with the same platform. Print the raw number as there's no need for the driver to check a

[PATCH 1/2] drm/i915/display: Also print raw step number

GMD_ID is already parsed down to the step. Don't omit that information in the display engine debug info. This helps to double check the stepping is parsed correctly. For earlier platforms, it will start printing the entire version too (which should be 0), as a rel == 0 doesn't mean it doesn't have

Re: (subset) [PATCH] drm/crtc: fix uninitialized variable use

On Fri, 08 Dec 2023 15:12:38 +0200, Jani Nikula wrote: > Commit 3823119b9c2b ("drm/crtc: Fix uninit-value bug in > drm_mode_setcrtc") was supposed to fix use of an uninitialized variable, > but introduced another. > > num_connectors is only initialized if crtc_req->count_connectors > 0, > but it's

✗ Fi.CI.BAT: failure for drm/crtc: fix uninitialized variable use

== Series Details == Series: drm/crtc: fix uninitialized variable use URL : https://patchwork.freedesktop.org/series/127569/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13999 -> Patchwork_127569v1 Summary --- **FAI

Re: [PATCH] drm/i915: fix display ver 12-13 fault error handling

On Fri, Dec 08, 2023 at 01:20:08PM +0200, Jani Nikula wrote: > Unless I'm completely misreading the bspec, there are no defined bits > for plane gtt fault errors in DE PIPE IIR for a display versions > 12-14. This would explain why DG2 in the linked bug is getting thousands > of fault errors. I th

[PULL] drm-intel-gt-next

Hi Dave & Sima, A rather late first drm-intel-gt-next PR towards v6.8. As most significant change we have addition of the DRM fdinfo memory stats functionality. Then DG2 and MTL workaround additions and fixes and a few for older platforms as well. PMU WARN_ON splat cleanup. The rest is mostly co

✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915/display: Also print raw step number

== Series Details == Series: series starting with [1/2] drm/i915/display: Also print raw step number URL : https://patchwork.freedesktop.org/series/127571/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/display: Also print raw step number

== Series Details == Series: series starting with [1/2] drm/i915/display: Also print raw step number URL : https://patchwork.freedesktop.org/series/127571/ State : failure == Summary == CI Bug Log - changes from CI_DRM_14000 -> Patchwork_127571v1 ===

✓ Fi.CI.BAT: success for drm/i915: fix display ver 12-13 fault error handling (rev2)

== Series Details == Series: drm/i915: fix display ver 12-13 fault error handling (rev2) URL : https://patchwork.freedesktop.org/series/127564/ State : success == Summary == CI Bug Log - changes from CI_DRM_14000 -> Patchwork_127564v2 Summa

✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7) URL : https://patchwork.freedesktop.org/series/126998/ State : warning == Summary == Error: dim checkpatch failed 38e14b399a56 drm/i915/gem: Atomically invalidate userptr on mmu-notifier -:117: WARN

✗ Fi.CI.SPARSE: warning for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7) URL : https://patchwork.freedesktop.org/series/126998/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [PATCH 1/2] drm/i915/display: Also print raw step number

On Fri, Dec 08, 2023 at 06:31:36AM -0800, Lucas De Marchi wrote: > GMD_ID is already parsed down to the step. Don't omit that information > in the display engine debug info. This helps to double check the > stepping is parsed correctly. > > For earlier platforms, it will start printing the entire

Re: [PATCH 2/2] drm/i915/display: Print PICA version

On Fri, Dec 08, 2023 at 06:31:37AM -0800, Lucas De Marchi wrote: > The PICA_DEVICE_ID follows the same format as other GMD_ID registers > (graphics, display and media). Currently the only use for it is > informational for developers while checking the differences between > machines with the same pl

✗ Fi.CI.BAT: failure for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev7) URL : https://patchwork.freedesktop.org/series/126998/ State : failure == Summary == CI Bug Log - changes from CI_DRM_14000 -> Patchwork_126998v7

Re: [Intel-gfx] [PATCH] drm/edid: also call add modes in EDID connector update fallback

On Thu, Dec 07, 2023 at 11:38:21AM +0200, Jani Nikula wrote: > When the separate add modes call was added back in commit c533b5167c7e > ("drm/edid: add separate drm_edid_connector_add_modes()"), it failed to > address drm_edid_override_connector_update(). Also call add modes there. > > Reported-by

Re: [PATCH] drm/i915: Fix ADL+ tiled plane stride when the POT stride is smaller than the original

On Mon, Dec 04, 2023 at 10:24:43PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > plane_view_scanout_stride() currently assumes that we had to pad the > mapping stride with dummy pages in order to align it. But that is not > the case if the original fb stride exceeds the aligned stride use

RE: [PATCH 3/3] drm/i915/mtl: Rename the link_bit_rate to clock in C20 pll_state

Thank you for the review. With clean CI pushed the patches upstream. Regards, Radhakrishna Sripada > -Original Message- > From: Kahola, Mika > Sent: Friday, December 8, 2023 4:01 AM > To: Sripada, Radhakrishna ; intel- > g...@lists.freedesktop.org > Cc: Taylor, Clinton A > Subject: RE:

Re: ✗ Fi.CI.BAT: failure for series starting with [v3,1/3] drm/i915/dp: Use LINK_QUAL_PATTERN_* Phy test pattern names

On Thu, 2023-12-07 at 03:14 +, Patchwork wrote: > Patch Details > Series: series starting with [v3,1/3] drm/i915/dp: Use > LINK_QUAL_PATTERN_* Phy test pattern names > URL: https://patchwork.freedesktop.org/series/127465/ > State:failure > Details: > https://intel-gfx-ci.01

Re: [PATCH 2/2] drm/i915/display: Print PICA version

On Fri, Dec 08, 2023 at 10:02:53AM -0800, Matt Roper wrote: On Fri, Dec 08, 2023 at 06:31:37AM -0800, Lucas De Marchi wrote: The PICA_DEVICE_ID follows the same format as other GMD_ID registers (graphics, display and media). Currently the only use for it is informational for developers while che

Re: [PATCH 2/2] drm/i915/display: Print PICA version

On Fri, Dec 08, 2023 at 01:46:09PM -0600, Lucas De Marchi wrote: > On Fri, Dec 08, 2023 at 10:02:53AM -0800, Matt Roper wrote: > > On Fri, Dec 08, 2023 at 06:31:37AM -0800, Lucas De Marchi wrote: > > > The PICA_DEVICE_ID follows the same format as other GMD_ID registers > > > (graphics, display and

✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8) URL : https://patchwork.freedesktop.org/series/126998/ State : warning == Summary == Error: dim checkpatch failed c3296c836ffd drm/i915/gem: Atomically invalidate userptr on mmu-notifier -:117: WARN

✗ Fi.CI.SPARSE: warning for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8) URL : https://patchwork.freedesktop.org/series/126998/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.BAT: failure for drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8)

== Series Details == Series: drm/i915/gem: Atomically invalidate userptr on mmu-notifier (rev8) URL : https://patchwork.freedesktop.org/series/126998/ State : failure == Summary == CI Bug Log - changes from CI_DRM_14001 -> Patchwork_126998v8

Re: [PATCH 1/3] drm: Add Adaptive Sync SDP logging

Hi Mitul, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on drm-intel/for-linux-next-fixes drm/drm-next drm-tip/drm-tip linus/master v6.7-rc4 next-20231208] [If your patch is applied to the wrong git tree

✗ Fi.CI.IGT: failure for drm/i915/hdcp: Fail Repeater authentication if Type1 device not present (rev2)

== Series Details == Series: drm/i915/hdcp: Fail Repeater authentication if Type1 device not present (rev2) URL : https://patchwork.freedesktop.org/series/127414/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13990_full -> Patchwork_127414v2_full =