[Intel-gfx] [CI v2 0/4] drm/i915/guc: Improve CTB error handling

There was a gap in handling MMIO result from CTB (de)registration and while fixing it improve some other error reports. Signed-off-by: Michal Wajdeczko Reviewed-by: Daniel Vetter v2: collect latest CI results Michal Wajdeczko (4): drm/i915/guc: Verify result from CTB (de)register action dr

[Intel-gfx] [CI v2 3/4] drm/i915/guc: Print error name on CTB send failure

Instead of plain error value (%d) print more user friendly error name (%pe). Signed-off-by: Michal Wajdeczko Reviewed-by: Daniel Vetter --- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c

[Intel-gfx] [CI v2 1/4] drm/i915/guc: Verify result from CTB (de)register action

In commit b839a869dfc9 ("drm/i915/guc: Add support for data reporting in GuC responses") we missed the hypothetical case that GuC might return positive non-zero value as success data. While that would be lucky treated as error case, and at the end will result in reporting valid -EIO, in the meanti

[Intel-gfx] [CI v2 4/4] drm/i915/guc: Move and improve error message for missed CTB reply

If we timeout waiting for a CT reply we print very simple error message. Improve that and by moving error reporting to the caller we can use CT_ERROR instead of DRM_ERROR and report just fence as error code will be reported later anyway. Signed-off-by: Michal Wajdeczko Reviewed-by: Daniel Vetter

[Intel-gfx] [CI v2 2/4] drm/i915/guc: Print error name on CTB (de)registration failure

Instead of plain error value (%d) print more user friendly error name (%pe). Signed-off-by: Michal Wajdeczko Reviewed-by: Daniel Vetter --- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Improve CTB error handling (rev3)

== Series Details == Series: drm/i915/guc: Improve CTB error handling (rev3) URL : https://patchwork.freedesktop.org/series/92118/ State : success == Summary == CI Bug Log - changes from CI_DRM_10644 -> Patchwork_21161 Summary --- **

[Intel-gfx] [PATCH] drm/i915: Use fixed offset for PTEs location

We assumed that for all modern GENs the PTEs and register space are split in the GTTMMADR BAR, but while it is true, we should rather use fixed offset as it is defined in the specification. Bspec: 4409, 4457, 4604, 11181, 9027, 13246, 13321, 44980 Signed-off-by: Michal Wajdeczko Cc: CQ Tang Cc:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Improve CTB error handling (rev3)

== Series Details == Series: drm/i915/guc: Improve CTB error handling (rev3) URL : https://patchwork.freedesktop.org/series/92118/ State : success == Summary == CI Bug Log - changes from CI_DRM_10644_full -> Patchwork_21161_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use fixed offset for PTEs location

== Series Details == Series: drm/i915: Use fixed offset for PTEs location URL : https://patchwork.freedesktop.org/series/95074/ State : success == Summary == CI Bug Log - changes from CI_DRM_10644 -> Patchwork_21162 Summary --- **SUC

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Use fixed offset for PTEs location

== Series Details == Series: drm/i915: Use fixed offset for PTEs location URL : https://patchwork.freedesktop.org/series/95074/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10644_full -> Patchwork_21162_full Summary --

[Intel-gfx] linux-next: build warning after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (htmldocs) produced these warnings: include/drm/drm_edid.h:530: warning: Function parameter or member 'vend_chr_1' not described in 'drm_edid_encode_panel_id' include/drm/drm_edid.h:530: warning: Excess function parameter 'vend_ch