drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
Subsystems (7)
PATCH 1/3 drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
From: Ville Syrjälä <[email protected]>
Put the vblank timestamping constants update loop into its own function. It has no business living inside drm_atomic_helper_update_legacy_modeset_state() so we'll be wanting to move it out entirely. As a first step we'll still call it from drm_atomic_helper_update_legacy_modeset_state().
--- drivers/gpu/drm/drm_atomic_helper.c | 22 +++++++++++++++++++++- include/drm/drm_atomic_helper.h | 3 +++ 2 files changed, 24 insertions(+), 1 deletion(-)
drivers/gpu/drm/drm_atomic_helper.c +21 -1
@@ -1186,13 +1186,33 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->x = new_plane_state->src_x >>16 ; crtc->y = new_plane_state->src_y >>16 ; } + } +drm_atomic_helper_calc_timestamping_constants (old_state); +} +EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state); + +/** +* drm_atomic_helper_calc_timestamping_constants - update vblank timestamping constants +* @state: atomic state object +* +* Updates the timestamping constants used for precise vblank timestamps +* by calling drm_calc_timestamping_constants() for all enabled crtcs in @state. +*/ +void drm_atomic_helper_calc_timestamping_constants (struct drm_atomic_state *state) +{ +struct drm_crtc_state *new_crtc_state; +struct drm_crtc *crtc; +int i; + +/* set legacy state in the crtc structure */ +for_each_new_crtc_in_state (state, crtc, new_crtc_state, i) {if (new_crtc_state->enable)drm_calc_timestamping_constants (crtc, &new_crtc_state->adjusted_mode); } } -EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state); +EXPORT_SYMBOL (drm_atomic_helper_calc_timestamping_constants);static void crtc_set_mode (struct drm_device *dev,struct drm_atomic_state *old_state)
include/drm/drm_atomic_helper.h +3 -0
@@ -74,6 +74,9 @@ void drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, struct drm_atomic_state *old_state); +void +drm_atomic_helper_calc_timestamping_constants (struct drm_atomic_state *state); +void drm_atomic_helper_commit_modeset_disables (struct drm_device *dev,struct drm_atomic_state *state); void drm_atomic_helper_commit_modeset_enables(struct drm_device *dev,
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/3 drm/atomic-helper: Remove the timestamping constant update from drm_atomic_helper_update_legacy_modeset_state()
From: Ville Syrjälä <[email protected]>
The timestamping constants have nothing to do with any legacy state so should not be updated from drm_atomic_helper_update_legacy_modeset_state().
Let's make everyone call drm_atomic_helper_calc_timestamping_constants() directly instead of relying on drm_atomic_helper_update_legacy_modeset_state() to call it.
@@
expression S;
@@
- drm_atomic_helper_calc_timestamping_constants(S);
@@
expression D, S;
@@
drm_atomic_helper_update_legacy_modeset_state(D, S);
+ drm_atomic_helper_calc_timestamping_constants(S);
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 1 + drivers/gpu/drm/drm_atomic_helper.c | 7 ++----- drivers/gpu/drm/i915/display/intel_display.c | 1 + drivers/gpu/drm/nouveau/dispnv50/disp.c | 1 + 4 files changed, 5 insertions(+), 5 deletions(-)
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +1 -0
@@ -7397,6 +7397,7 @@ static void amdgpu_dm_atomic_commit_tail(struct drm_atomic_state *state)int crtc_disable_count =0 ;drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state); dm_state =dm_atomic_get_new_state (state);if (dm_state && dm_state->context) {
drivers/gpu/drm/drm_atomic_helper.c +2 -5
@@ -1115,9 +1115,7 @@ disable_outputs(struct drm_device *dev, struct drm_atomic_state *old_state)* @old_state: atomic state object with old state structures * * This function updates all the various legacy modeset state pointers in -* connectors, encoders and CRTCs. It also updates the timestamping constants -* used for precise vblank timestamps by calling -* drm_calc_timestamping_constants(). +* connectors, encoders and CRTCs. * * Drivers can use this for building their own atomic commit if they don't have * a pure helper-based modeset implementation.
@@ -1187,8 +1185,6 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->y = new_plane_state->src_y >>16 ; } } - -drm_atomic_helper_calc_timestamping_constants (old_state); }EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state);
@@ -1296,6 +1292,7 @@ void drm_atomic_helper_commit_modeset_disables(struct drm_device *dev,disable_outputs (dev, old_state);drm_atomic_helper_update_legacy_modeset_state (dev, old_state); +drm_atomic_helper_calc_timestamping_constants (old_state);crtc_set_mode (dev, old_state); }
drivers/gpu/drm/i915/display/intel_display.c +1 -0
@@ -15578,6 +15578,7 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); +drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);
drivers/gpu/drm/nouveau/dispnv50/disp.c +1 -0
@@ -2069,6 +2069,7 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state *state)drm_atomic_helper_wait_for_fences (dev, state, false);drm_atomic_helper_wait_for_dependencies (state);drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state);if (atom->lock_core)mutex_lock (&disp->mutex);
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 2/3] drm/atomic-helper: Remove the timestamping constant update from drm_atomic_helper_update_legacy_modeset_state()
Quoted 15 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
The timestamping constants have nothing to do with any legacy state so should not be updated from
drm_atomic_helper_update_legacy_modeset_state().Let's make everyone call
drm_atomic_helper_calc_timestamping_constants()directly instead of relying ondrm_atomic_helper_update_legacy_modeset_state()to call it.@@
expression S;
@@
-drm_atomic_helper_calc_timestamping_constants(S);
Quoted 7 lines
@@
expression D, S;
@@
drm_atomic_helper_update_legacy_modeset_state(D, S);
+drm_atomic_helper_calc_timestamping_constants(S);Signed-off-by Ville Syrjälä <[email protected]>
I think the kerneldoc for drm_crtc_vblank_helper_get_vblank/_timestamp_internal (both of them) also needs to be updated to mention the new function. With that fixed:
Quoted 82 lines
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 1 + drivers/gpu/drm/drm_atomic_helper.c | 7 ++----- drivers/gpu/drm/i915/display/intel_display.c | 1 + drivers/gpu/drm/nouveau/dispnv50/disp.c | 1 + 4 files changed, 5 insertions(+), 5 deletions(-)drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +1
-0@@ -7397,6 +7397,7 @@ static void amdgpu_dm_atomic_commit_tail(struct drm_atomic_state *state)int crtc_disable_count =0 ;drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state); dm_state =dm_atomic_get_new_state (state);if (dm_state && dm_state->context) {drivers/gpu/drm/drm_atomic_helper.c +2
-5@@ -1115,9 +1115,7 @@ disable_outputs(struct drm_device *dev, struct drm_atomic_state *old_state)* @old_state: atomic state object with old state structures * * This function updates all the various legacy modeset state pointers in -* connectors, encoders and CRTCs. It also updates the timestamping constants -* used for precise vblank timestamps by calling -* drm_calc_timestamping_constants(). +* connectors, encoders and CRTCs. * * Drivers can use this for building their own atomic commit if they don't have * a pure helper-based modeset implementation. @@ -1187,8 +1185,6 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->y = new_plane_state->src_y >>16 ; } } - -drm_atomic_helper_calc_timestamping_constants (old_state); }EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state);@@ -1296,6 +1292,7 @@ void drm_atomic_helper_commit_modeset_disables(struct drm_device *dev,disable_outputs (dev, old_state);drm_atomic_helper_update_legacy_modeset_state (dev, old_state); +drm_atomic_helper_calc_timestamping_constants (old_state);crtc_set_mode (dev, old_state); }drivers/gpu/drm/i915/display/intel_display.c +1
-0@@ -15578,6 +15578,7 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); +drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);drivers/gpu/drm/nouveau/dispnv50/disp.c +1
-0@@ -2069,6 +2069,7 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state *state)drm_atomic_helper_wait_for_fences (dev, state, false);drm_atomic_helper_wait_for_dependencies (state);drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state);if (atom->lock_core)mutex_lock (&disp->mutex);Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 2/3] drm/atomic-helper: Remove the timestamping constant update from drm_atomic_helper_update_legacy_modeset_state()
Quoted 22 lines · Daniel Vetter
Quoted 21 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
The timestamping constants have nothing to do with any legacy state so should not be updated from
drm_atomic_helper_update_legacy_modeset_state().Let's make everyone call
drm_atomic_helper_calc_timestamping_constants()directly instead of relying ondrm_atomic_helper_update_legacy_modeset_state()to call it.@@
expression S;
@@
-drm_atomic_helper_calc_timestamping_constants(S);@@
expression D, S;
@@
drm_atomic_helper_update_legacy_modeset_state(D, S);
+drm_atomic_helper_calc_timestamping_constants(S);
Quoted 7 lines
Quoted 1 line
Signed-off-by Ville Syrjälä <[email protected]>I think the kerneldoc for drm_crtc_vblank_helper_get_vblank/_timestamp_internal (both of them) also needs to be updated to mention the new function. With that fixed:
Reviewed-by Daniel Vetter <[email protected]>
Fixed the docs while applying. Thanks for the review.
Quoted 89 lines
Quoted 84 lines
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 1 + drivers/gpu/drm/drm_atomic_helper.c | 7 ++----- drivers/gpu/drm/i915/display/intel_display.c | 1 + drivers/gpu/drm/nouveau/dispnv50/disp.c | 1 + 4 files changed, 5 insertions(+), 5 deletions(-)drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +1
-0@@ -7397,6 +7397,7 @@ static void amdgpu_dm_atomic_commit_tail(struct drm_atomic_state *state)int crtc_disable_count =0 ;drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state); dm_state =dm_atomic_get_new_state (state);if (dm_state && dm_state->context) {drivers/gpu/drm/drm_atomic_helper.c +2
-5@@ -1115,9 +1115,7 @@ disable_outputs(struct drm_device *dev, struct drm_atomic_state *old_state)* @old_state: atomic state object with old state structures * * This function updates all the various legacy modeset state pointers in -* connectors, encoders and CRTCs. It also updates the timestamping constants -* used for precise vblank timestamps by calling -* drm_calc_timestamping_constants(). +* connectors, encoders and CRTCs. * * Drivers can use this for building their own atomic commit if they don't have * a pure helper-based modeset implementation. @@ -1187,8 +1185,6 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->y = new_plane_state->src_y >>16 ; } } - -drm_atomic_helper_calc_timestamping_constants (old_state); }EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state);@@ -1296,6 +1292,7 @@ void drm_atomic_helper_commit_modeset_disables(struct drm_device *dev,disable_outputs (dev, old_state);drm_atomic_helper_update_legacy_modeset_state (dev, old_state); +drm_atomic_helper_calc_timestamping_constants (old_state);crtc_set_mode (dev, old_state); }drivers/gpu/drm/i915/display/intel_display.c +1
-0@@ -15578,6 +15578,7 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); +drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);drivers/gpu/drm/nouveau/dispnv50/disp.c +1
-0@@ -2069,6 +2069,7 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state *state)drm_atomic_helper_wait_for_fences (dev, state, false);drm_atomic_helper_wait_for_dependencies (state);drm_atomic_helper_update_legacy_modeset_state (dev, state); +drm_atomic_helper_calc_timestamping_constants (state);if (atom->lock_core)mutex_lock (&disp->mutex);Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfxSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/3 drm/i915: Drop the drm_atomic_helper_calc_timestamping_constants() call
In reply to Ville SyrjalaFrom: Ville Syrjälä <[email protected]>
We update the timestamping constants per-crtc explicitly in intel_crtc_update_active_timings(). Furtermore the helper will use uapi.adjusted_mode whereas we want hw.adjusted_mode. Thus let's drop the helper call an rely on what we already have in intel_crtc_update_active_timings(). We can now also drop the hw.adjusted_mode -> uapi.adjusted_mode copy hack that was added to keep the helper from deriving the timestamping constants from the wrong thing.
--- drivers/gpu/drm/i915/display/intel_display.c | 7 ------- 1 file changed, 7 deletions(-)
drivers/gpu/drm/i915/display/intel_display.c +0 -7
@@ -13472,12 +13472,6 @@ intel_modeset_pipe_config(struct intel_crtc_state *pipe_config)"hw max bpp: %i, pipe bpp: %i, dithering: %i\n" , base_bpp, pipe_config->pipe_bpp, pipe_config->dither); -/* -* Make drm_calc_timestamping_constants in -* drm_atomic_helper_update_legacy_modeset_state() happy -*/ - pipe_config->uapi.adjusted_mode = pipe_config->hw.adjusted_mode; -return 0 ; }
@@ -15578,7 +15572,6 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); -drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);
Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 3/3] drm/i915: Drop the drm_atomic_helper_calc_timestamping_constants() call
Quoted 11 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
We update the timestamping constants per-crtc explicitly in
intel_crtc_update_active_timings(). Furtermore the helper will use uapi.adjusted_mode whereas we want hw.adjusted_mode. Thus let's drop the helper call an rely on what we already have inintel_crtc_update_active_timings(). We can now also drop the hw.adjusted_mode -> uapi.adjusted_mode copy hack that was added to keep the helper from deriving the timestamping constants from the wrong thing.
Quoted 1 line
Signed-off-by Ville Syrjälä <[email protected]>
Does this fix some CI fail? I'd kinda expect/hope for that ...
Anyway looks like a good idea to not mess with the uapi state like this.
Quoted 36 lines
--- drivers/gpu/drm/i915/display/intel_display.c | 7 ------- 1 file changed, 7 deletions(-)drivers/gpu/drm/i915/display/intel_display.c +0
-7@@ -13472,12 +13472,6 @@ intel_modeset_pipe_config(struct intel_crtc_state *pipe_config)"hw max bpp: %i, pipe bpp: %i, dithering: %i\n" , base_bpp, pipe_config->pipe_bpp, pipe_config->dither); -/* -* Make drm_calc_timestamping_constants in -* drm_atomic_helper_update_legacy_modeset_state() happy -*/ - pipe_config->uapi.adjusted_mode = pipe_config->hw.adjusted_mode; -return 0 ; }@@ -15578,7 +15572,6 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); -drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 3/3] drm/i915: Drop the drm_atomic_helper_calc_timestamping_constants() call
Quoted 12 lines · Daniel Vetter
Quoted 11 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
We update the timestamping constants per-crtc explicitly in
intel_crtc_update_active_timings(). Furtermore the helper will use uapi.adjusted_mode whereas we want hw.adjusted_mode. Thus let's drop the helper call an rely on what we already have inintel_crtc_update_active_timings(). We can now also drop the hw.adjusted_mode -> uapi.adjusted_mode copy hack that was added to keep the helper from deriving the timestamping constants from the wrong thing.
Quoted 3 lines
Quoted 1 line
Signed-off-by Ville Syrjälä <[email protected]>Does this fix some CI fail? I'd kinda expect/hope for that ...
Nah. Just trying to get rid of some of the confusing stuff before we add even more confusing stuff for bigjoiner.
Quoted 46 lines
Anyway looks like a good idea to not mess with the uapi state like this.
Reviewed-by Daniel Vetter <[email protected]>Quoted 36 lines
--- drivers/gpu/drm/i915/display/intel_display.c | 7 ------- 1 file changed, 7 deletions(-)drivers/gpu/drm/i915/display/intel_display.c +0
-7@@ -13472,12 +13472,6 @@ intel_modeset_pipe_config(struct intel_crtc_state *pipe_config)"hw max bpp: %i, pipe bpp: %i, dithering: %i\n" , base_bpp, pipe_config->pipe_bpp, pipe_config->dither); -/* -* Make drm_calc_timestamping_constants in -* drm_atomic_helper_update_legacy_modeset_state() happy -*/ - pipe_config->uapi.adjusted_mode = pipe_config->hw.adjusted_mode; -return 0 ; }@@ -15578,7 +15572,6 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state)if (state->modeset) {drm_atomic_helper_update_legacy_modeset_state (dev, &state->base); -drm_atomic_helper_calc_timestamping_constants (&state->base);intel_set_cdclk_pre_plane_update (state);Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfxSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
URL : https://patchwork.freedesktop.org/series/81419/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1666:65: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1674:55: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1675:50: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1676:50: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1677:56: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1679:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1680:45: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1681:51: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1682:55: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1683:57: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1685:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1686:53: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1688:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1690:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1691:46: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1695:73: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1697:33: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1699:33: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1710:73: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:264:16: error: incompatible types in comparison expression (different type sizes): +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:264:16: unsigned long * +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:264:16: unsigned long long * +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:522:39: warning: cast removes address space '__iomem' of expression +drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:542:31: warning: cast removes address space '__iomem' of expression +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1176:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1181:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1181:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1181:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1183:36: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1260:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1260:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1260:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1266:37: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1292:41: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1294:39: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1298:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1299:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1302:17: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:796:25: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:800:23: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:801:23: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:804:30: warning: cast to restricted __le32 +drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:807:28: warning: cast to restricted __le32 +drivers/gpu/drm/selftests/test-drm_damage_helper.c:244:25: warning: Using plain integer as NULL pointer +drivers/gpu/drm/selftests/test-drm_damage_helper.c:268:23: warning: Using plain integer as NULL pointer
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
URL : https://patchwork.freedesktop.org/series/81419/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8971 -> Patchwork_18448
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/index.html
Known issues
------------
Here are the changes found in Patchwork_18448 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0:
- fi-glk-dsi: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-glk-dsi/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-glk-dsi/igt@[email protected]
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-bsw-kefka/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-bsw-kefka/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][5] -> [FAIL][6] ([i915#1372])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-kbl-7500u/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-kbl-7500u/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
- fi-icl-u2: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-icl-u2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-icl-u2/igt@[email protected]
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-bsw-nick: [INCOMPLETE][9] ([i915#1250] / [i915#1436]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-bsw-nick/igt@debugfs_test@read_all_entries.html
#### Warnings ####
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][11] ([i915#62] / [i915#92]) -> [DMESG-WARN][12] ([i915#62] / [i915#92] / [i915#95]) +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-kbl-x1275/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-kbl-x1275/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][13] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][14] ([i915#62] / [i915#92]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/fi-kbl-x1275/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1250]: https://gitlab.freedesktop.org/drm/intel/issues/1250
[i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (45 -> 39)
------------------------------
Additional (2): fi-tgl-y fi-gdg-551
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-icl-dsi fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8971 -> Patchwork_18448
CI-20190529: 20190529
CI_DRM_8971: f274be2fef06d17db45aa72ab5bc571621de5334 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5779: f52bf19b5f02d52fc3e201c6467ec3f511227fba @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18448: 7ae6d1d023175e4cd663ac3976197e718c75a7a2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
7ae6d1d02317 drm/i915: Drop the drm_atomic_helper_calc_timestamping_constants() callc3c73f3b0192 drm/atomic-helper: Remove the timestamping constant update from drm_atomic_helper_update_legacy_modeset_state() 19866c85f05b drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 9 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
Put the vblank timestamping constants update loop into its own function. It has no business living inside
drm_atomic_helper_update_legacy_modeset_state()so we'll be wanting to move it out entirely. As a first step we'll still call it fromdrm_atomic_helper_update_legacy_modeset_state().Signed-off-by Ville Syrjälä <[email protected]>
Quoted 65 lines
--- drivers/gpu/drm/drm_atomic_helper.c | 22 +++++++++++++++++++++- include/drm/drm_atomic_helper.h | 3 +++ 2 files changed, 24 insertions(+), 1 deletion(-)drivers/gpu/drm/drm_atomic_helper.c +21
-1@@ -1186,13 +1186,33 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->x = new_plane_state->src_x >>16 ; crtc->y = new_plane_state->src_y >>16 ; } + } +drm_atomic_helper_calc_timestamping_constants (old_state); +} +EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state); + +/** +* drm_atomic_helper_calc_timestamping_constants - update vblank timestamping constants +* @state: atomic state object +* +* Updates the timestamping constants used for precise vblank timestamps +* by calling drm_calc_timestamping_constants() for all enabled crtcs in @state. +*/ +void drm_atomic_helper_calc_timestamping_constants (struct drm_atomic_state *state) +{ +struct drm_crtc_state *new_crtc_state; +struct drm_crtc *crtc; +int i; + +/* set legacy state in the crtc structure */ +for_each_new_crtc_in_state (state, crtc, new_crtc_state, i) {if (new_crtc_state->enable)drm_calc_timestamping_constants (crtc, &new_crtc_state->adjusted_mode); } } -EXPORT_SYMBOL (drm_atomic_helper_update_legacy_modeset_state); +EXPORT_SYMBOL (drm_atomic_helper_calc_timestamping_constants);static void crtc_set_mode (struct drm_device *dev,struct drm_atomic_state *old_state)include/drm/drm_atomic_helper.h +3
-0@@ -74,6 +74,9 @@ void drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, struct drm_atomic_state *old_state); +void +drm_atomic_helper_calc_timestamping_constants (struct drm_atomic_state *state); +void drm_atomic_helper_commit_modeset_disables (struct drm_device *dev,struct drm_atomic_state *state); void drm_atomic_helper_commit_modeset_enables(struct drm_device *dev,Signature · 6 lines
2.26.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
URL : https://patchwork.freedesktop.org/series/81419/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8971_full -> Patchwork_18448_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_18448_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_18448_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_18448_full:
### IGT changes ###
#### Possible regressions ####
* igt@perf_pmu@rc6-runtime-pm-long:
- shard-hsw: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-hsw1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-hsw7/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@kms_writeback@writeback-invalid-parameters}:
- shard-tglb: NOTRUN -> [SKIP][3] +3 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-tglb2/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_18448_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_reloc@basic-many-active@vecs0:
- shard-glk: [PASS][4] -> [FAIL][5] ([i915#2389]) +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-glk1/igt@gem_exec_reloc@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-glk7/igt@gem_exec_reloc@[email protected]
* igt@gem_exec_whisper@basic-fds-priority-all:
- shard-glk: [PASS][6] -> [DMESG-WARN][7] ([i915#118] / [i915#95])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-glk4/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-glk6/igt@[email protected]
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-skl: [PASS][8] -> [TIMEOUT][9] ([i915#1958] / [i915#2424])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl4/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl6/igt@[email protected]
* igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@edp-1-pipe-a:
- shard-skl: [PASS][10] -> [DMESG-WARN][11] ([i915#1982]) +3 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl8/igt@kms_atomic_transition@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl5/igt@kms_atomic_transition@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x42-sliding:
- shard-glk: [PASS][12] -> [FAIL][13] ([i915#54])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-glk1/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-glk7/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-skl: [PASS][14] -> [INCOMPLETE][15] ([i915#300])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl3/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl7/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-hdmi-a2:
- shard-glk: [PASS][16] -> [FAIL][17] ([i915#79])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-glk1/igt@kms_flip@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-glk9/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-tglb: [PASS][18] -> [DMESG-WARN][19] ([i915#1982]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-tglb3/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-tglb6/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][20] -> [SKIP][21] ([fdo#109441]) +3 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-iclb6/igt@kms_psr@psr2_cursor_plane_move.html
* igt@perf@polling:
- shard-skl: [PASS][22] -> [FAIL][23] ([i915#1542])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl9/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl10/igt@[email protected]
#### Possible fixes ####
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][24] ([i915#1436] / [i915#716]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl2/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl4/igt@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-0:
- shard-glk: [DMESG-WARN][26] ([i915#1982]) -> [PASS][27]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-glk3/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-glk1/igt@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-iclb: [DMESG-WARN][28] ([i915#1982]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-iclb3/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-iclb5/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-skl: [INCOMPLETE][30] ([i915#300]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl5/igt@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl6/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-256x256-left-edge:
- shard-apl: [DMESG-WARN][32] ([i915#1635] / [i915#1982]) -> [PASS][33] +2 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-apl1/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-apl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min:
- shard-skl: [FAIL][34] ([fdo#108145] / [i915#265]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl4/igt@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl6/igt@[email protected]
* igt@kms_plane_scaling@pipe-a-plane-scaling:
- shard-skl: [DMESG-WARN][36] ([i915#1982]) -> [PASS][37] +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-skl7/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-skl5/igt@[email protected]
* igt@perf_pmu@module-unload:
- shard-hsw: [DMESG-WARN][38] ([i915#1982]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8971/shard-hsw1/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/shard-hsw4/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2424]: https://gitlab.freedesktop.org/drm/intel/issues/2424
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#300]: https://gitlab.freedesktop.org/drm/intel/issues/300
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (12 -> 11)
------------------------------
Missing (1): pig-snb-2600
Build changes
-------------
* Linux: CI_DRM_8971 -> Patchwork_18448
CI-20190529: 20190529
CI_DRM_8971: f274be2fef06d17db45aa72ab5bc571621de5334 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5779: f52bf19b5f02d52fc3e201c6467ec3f511227fba @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18448: 7ae6d1d023175e4cd663ac3976197e718c75a7a2 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18448/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx