[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Decouple engine->sanitize callback on removing the status page

== Series Details == Series: drm/i915: Decouple engine->sanitize callback on removing the status page URL : https://patchwork.freedesktop.org/series/101679/ State : success == Summary == CI Bug Log - changes from CI_DRM_11398 -> Patchwork_22656

Re: [Intel-gfx] [v8 3/5] drm/edid: read HF-EEODB ext block

On Wed, 23 Mar 2022, Simon Ser wrote: > On Wednesday, March 23rd, 2022 at 13:02, Jani Nikula > wrote: > >> Simon and Daniel also tell me on IRC we can't just modify the base block >> extension count to match HF-EEODB to dodge the problem, because the EDID >> gets exposed to userspace. > > I'm

Re: [Intel-gfx] [v8 3/5] drm/edid: read HF-EEODB ext block

On Wednesday, March 23rd, 2022 at 13:02, Jani Nikula wrote: > Simon and Daniel also tell me on IRC we can't just modify the base block > extension count to match HF-EEODB to dodge the problem, because the EDID > gets exposed to userspace. I'm not familiar how the EDID blob gets exposed to

Re: [Intel-gfx] [v8 3/5] drm/edid: read HF-EEODB ext block

On Wed, 23 Mar 2022, Jani Nikula wrote: > On Thu, 17 Mar 2022, Lee Shawn C wrote: >> According to HDMI 2.1 spec. >> >> "The HDMI Forum EDID Extension Override Data Block (HF-EEODB) >> is utilized by Sink Devices to provide an alternate method to >> indicate an EDID Extension Block count larger

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Decouple engine->sanitize callback on removing the status page

== Series Details == Series: drm/i915: Decouple engine->sanitize callback on removing the status page URL : https://patchwork.freedesktop.org/series/101679/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning:

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Decouple engine->sanitize callback on removing the status page

== Series Details == Series: drm/i915: Decouple engine->sanitize callback on removing the status page URL : https://patchwork.freedesktop.org/series/101679/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Decouple engine->sanitize callback on removing the status page

== Series Details == Series: drm/i915: Decouple engine->sanitize callback on removing the status page URL : https://patchwork.freedesktop.org/series/101679/ State : warning == Summary == $ dim checkpatch origin/drm-tip 716dbea36f93 drm/i915: Decouple engine->sanitize callback on removing the

[Intel-gfx] ✓ Fi.CI.BAT: success for Remove check for ComboPHY I/O voltage for DP source rate (rev5)

== Series Details == Series: Remove check for ComboPHY I/O voltage for DP source rate (rev5) URL : https://patchwork.freedesktop.org/series/96293/ State : success == Summary == CI Bug Log - changes from CI_DRM_11398 -> Patchwork_22655

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm: add a check to verify the size alignment (rev2)

== Series Details == Series: drm: add a check to verify the size alignment (rev2) URL : https://patchwork.freedesktop.org/series/101569/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11397_full -> Patchwork_22653_full

Re: [Intel-gfx] [PATCH v11] drm/amdgpu: add drm buddy support to amdgpu

Hi Arunpravin, Thank you for the patch! Yet something to improve: [auto build test ERROR on a678f97326454b60ffbbde6abf52d23997d71a27] url: https://github.com/0day-ci/linux/commits/Arunpravin-Paneer-Selvam/drm-amdgpu-add-drm-buddy-support-to-amdgpu/20220323-142749 base

[Intel-gfx] ✗ Fi.CI.DOCS: warning for Remove check for ComboPHY I/O voltage for DP source rate (rev5)

== Series Details == Series: Remove check for ComboPHY I/O voltage for DP source rate (rev5) URL : https://patchwork.freedesktop.org/series/96293/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning:

Re: [Intel-gfx] [PATCH] drm/i915: Decouple engine->sanitize callback on removing the status page

On Wed, 23 Mar 2022 at 09:44, Gwan-gyeong Mun wrote: > > From: Chris Wilson > > We have to be careful not to call into the submission backend's sanitize > callback if we abort the module load and free the status page. Since we > are only using the sanitize callback to cleanup the status page

Re: [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection

On Wed, 23 Mar 2022, "Lee, Shawn C" wrote: > On Wednesday, March 23, 2022 6:04 PM, Nikula, Jani > wrote : >>On Mon, 21 Mar 2022, Cooper Chiou wrote: >>> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio >>> information definition, but drm_detect_monitor_audio didn't filter it

[Intel-gfx] ✓ Fi.CI.BAT: success for Improve on resume time with VT-d enabled

== Series Details == Series: Improve on resume time with VT-d enabled URL : https://patchwork.freedesktop.org/series/101676/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397 -> Patchwork_22654 Summary ---

Re: [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection

On Wednesday, March 23, 2022 6:04 PM, Nikula, Jani wrote : >On Mon, 21 Mar 2022, Cooper Chiou wrote: >> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio >> information definition, but drm_detect_monitor_audio didn't filter it >> so that it caused eDP dummy audio card be

Re: [Intel-gfx] [v8 3/5] drm/edid: read HF-EEODB ext block

On Thu, 17 Mar 2022, Lee Shawn C wrote: > According to HDMI 2.1 spec. > > "The HDMI Forum EDID Extension Override Data Block (HF-EEODB) > is utilized by Sink Devices to provide an alternate method to > indicate an EDID Extension Block count larger than 1, while > avoiding the need to present a

[Intel-gfx] ✗ Fi.CI.DOCS: warning for Improve on resume time with VT-d enabled

== Series Details == Series: Improve on resume time with VT-d enabled URL : https://patchwork.freedesktop.org/series/101676/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning: 'intel_drrs_enable' not found

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Improve on resume time with VT-d enabled

== Series Details == Series: Improve on resume time with VT-d enabled URL : https://patchwork.freedesktop.org/series/101676/ 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/edid: fix CEA extension byte #3 parsing

Only an EDID CEA extension has byte #3, while the CTA DisplayID Data Block does not. Don't interpret bogus data for color formats. For most displays it's probably an unlikely scenario you'd have a CTA DisplayID Data Block without a CEA extension, but they do exist. Fixes: e28ad544f462

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve on resume time with VT-d enabled

== Series Details == Series: Improve on resume time with VT-d enabled URL : https://patchwork.freedesktop.org/series/101676/ State : warning == Summary == $ dim checkpatch origin/drm-tip f21c5b663eaf drm/i915: Wrap all access to i915_vma.node.start|size b41b256f8934 drm/i915: Introduce guard

[Intel-gfx] ✓ Fi.CI.BAT: success for drm: add a check to verify the size alignment (rev2)

== Series Details == Series: drm: add a check to verify the size alignment (rev2) URL : https://patchwork.freedesktop.org/series/101569/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397 -> Patchwork_22653 Summary

Re: [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection

On Mon, 21 Mar 2022, Cooper Chiou wrote: > In DisplayID v2.0 CTS data block 0x81 case, there is no any audio > information definition, but drm_detect_monitor_audio didn't filter > it so that it caused eDP dummy audio card be detected improperly. > > We observed this issue on some AUO/BOE eDP

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev2)

== Series Details == Series: drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev2) URL : https://patchwork.freedesktop.org/series/101565/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397_full -> Patchwork_22650_full

[Intel-gfx] [PATCH] drm/i915: Decouple engine->sanitize callback on removing the status page

From: Chris Wilson We have to be careful not to call into the submission backend's sanitize callback if we abort the module load and free the status page. Since we are only using the sanitize callback to cleanup the status page when we suspect its contents may have been lost (first load, upon

[Intel-gfx] [PATCH v5 2/2] drm/i915/intel_combo_phy: Print I/O voltage info

Print I/O voltage and process info for each combo phy ports. v2: Used drm_dbg_kms for logs. (Jani) Added names for different voltage levels. (Imre) v3: Used const char * for names. (Jani) v4: Dropped the procom values and changed commit msg (Imre) Suggested-by: Imre Deak Signed-off-by: Ankit

Re: [Intel-gfx] [v2] drm/edid: check basic audio support on CEA extension block

On Wed, 23 Mar 2022, Lee Shawn C wrote: > From: Cooper Chiou > > Tag code stored in bit7:5 for CTA block byte[3] is not the same as > CEA extension block definition. Only check CEA block has > basic audio support. > > Cc: Jani Nikula > Cc: Shawn C Lee > Cc: intel-gfx > Signed-off-by: Cooper

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm: add a check to verify the size alignment (rev2)

== Series Details == Series: drm: add a check to verify the size alignment (rev2) URL : https://patchwork.freedesktop.org/series/101569/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning: 'intel_drrs_enable' not

[Intel-gfx] ✗ Fi.CI.BAT: failure for Revert "drm/i915/dg2: Add relocation exception"

== Series Details == Series: Revert "drm/i915/dg2: Add relocation exception" URL : https://patchwork.freedesktop.org/series/101669/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11397 -> Patchwork_22652 Summary ---

[Intel-gfx] ✗ Fi.CI.DOCS: warning for Revert "drm/i915/dg2: Add relocation exception"

== Series Details == Series: Revert "drm/i915/dg2: Add relocation exception" URL : https://patchwork.freedesktop.org/series/101669/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning: 'intel_drrs_enable' not found

[Intel-gfx] [PATCH v4 3/3] drm/i915: Refine VT-d scanout workaround

From: Chris Wilson VT-d may cause overfetch of the scanout PTE, both before and after the vma (depending on the scanout orientation). bspec recommends that we provide a tile-row in either directions, and suggests using 168 PTE, warning that the accesses will wrap around the ends of the GGTT.

[Intel-gfx] [PATCH v4 2/3] drm/i915: Introduce guard pages to i915_vma

From: Chris Wilson Introduce the concept of padding the i915_vma with guard pages before and aft. The major consequence is that all ordinary uses of i915_vma must use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as the drm_mm_node will include the guard pages that

[Intel-gfx] [PATCH v4 1/3] drm/i915: Wrap all access to i915_vma.node.start|size

From: Chris Wilson We already wrap i915_vma.node.start for use with the GGTT, as there we can perform additional sanity checks that the node belongs to the GGTT and fits within the 32b registers. In the next couple of patches, we will introduce guard pages around the objects _inside_ the

[Intel-gfx] [PATCH v4 0/3] Improve on resume time with VT-d enabled

When DMAR / VT-d is enabled, the display engine uses overfetching, presumably to deal with the increased latency. To avoid display engine errors and DMAR faults, as a workaround the GGTT is populated with scatch PTEs when VT-d is enabled. However starting with gen10, Write-combined writing of

[Intel-gfx] Commit messages (was: [PATCH v11] drm/amdgpu: add drm buddy support to amdgpu)

Dear Christian, Am 23.03.22 um 08:42 schrieb Christian König: Am 23.03.22 um 07:42 schrieb Paul Menzel: Am 23.03.22 um 07:25 schrieb Arunpravin Paneer Selvam: - Remove drm_mm references and replace with drm buddy functionalities The commit message summary to me suggested, you can

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v2,1/4] drm/i915/display: Program PIPE_MBUS_DBOX_CTL with adl-p values

== Series Details == Series: series starting with [v2,1/4] drm/i915/display: Program PIPE_MBUS_DBOX_CTL with adl-p values URL : https://patchwork.freedesktop.org/series/101661/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397_full -> Patchwork_22649_full

[Intel-gfx] [PATCH] [topic/core-for-CI] Revert "drm/i915/dg2: Add relocation exception"

This reverts commit 904ebf2ba89edaeba5c7c10540e43dba63541dc6. Failures on dg2 tests were caused by invalid alignment when local memory was in use. Changes which adopt alignment according to gen were already merged in IGT so lets revert relocation temporary enabler for dg2. Keeping it is a little

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/amdgpu: add drm buddy support to amdgpu (rev2)

== Series Details == Series: drm/amdgpu: add drm buddy support to amdgpu (rev2) URL : https://patchwork.freedesktop.org/series/100908/ State : failure == Summary == CALLscripts/checksyscalls.sh CALLscripts/atomic/check-atomics.sh DESCEND objtool CHK

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/edid: overhaul CEA data block iteration

== Series Details == Series: drm/edid: overhaul CEA data block iteration URL : https://patchwork.freedesktop.org/series/101659/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397_full -> Patchwork_22648_full Summary

Re: [Intel-gfx] [PATCH] drm/i915/rps: Centralize computation of freq caps

On 23-03-2022 00:26, Ashutosh Dixit wrote: Freq caps (i.e. RP0, RP1 and RPn frequencies) are read from HW. However the formats (bit positions, widths, registers and units) of these vary for different generations with even more variations arriving in the future. In order not to have to do

Re: [Intel-gfx] [PATCH v11] drm/amdgpu: add drm buddy support to amdgpu

Dear Arunprivin, Thank you for your patch. Am 23.03.22 um 07:25 schrieb Arunpravin Paneer Selvam: - Remove drm_mm references and replace with drm buddy functionalities The commit message summary to me suggested, you can somehow use both allocators now. Two suggestions below: 1. Switch

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev2)

== Series Details == Series: drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev2) URL : https://patchwork.freedesktop.org/series/101565/ State : success == Summary == CI Bug Log - changes from CI_DRM_11397 -> Patchwork_22650

<    1   2