Re: [Intel-gfx] [PATCH v2 7/9] drm/i915: Properly write lock bw_state when it changes

On Thu, Mar 03, 2022 at 09:12:05PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > The current code also forgets to call intel_atomic_lock_global_state() > when other stuff besides the final min_cdlck changes in the state. > That means we may throw away data which actually has changed, and

[Intel-gfx] [PATCH v2 7/9] drm/i915: Properly write lock bw_state when it changes

From: Ville Syrjälä The current code also forgets to call intel_atomic_lock_global_state() when other stuff besides the final min_cdlck changes in the state. That means we may throw away data which actually has changed, and thus we can't be at all sure what the code ends up doing during subsequen