Re: [Intel-gfx] [08/11] drm/i915/guc: Wait for doorbell to be inactive before deallocating

2017-03-16 Thread Joonas Lahtinen
On pe, 2017-03-10 at 08:28 -0800, Oscar Mateo wrote: > Doorbell release flow requires that we wait for GEN8_DRB_VALID bit to go > to zero after updating db_status before we call the GuC to release the > doorbell. > > Kudos to Daniele for finding this out. > > Cc: Joonas Lahtinen

Re: [Intel-gfx] [08/11] drm/i915/guc: Wait for doorbell to be inactive before deallocating

2017-03-14 Thread Daniele Ceraolo Spurio
On 13/03/17 01:56, Oscar Mateo wrote: On 03/13/2017 04:46 AM, Chris Wilson wrote: On Fri, Mar 10, 2017 at 08:28:55AM -0800, Oscar Mateo wrote: Doorbell release flow requires that we wait for GEN8_DRB_VALID bit to go to zero after updating db_status before we call the GuC to release the

Re: [Intel-gfx] [08/11] drm/i915/guc: Wait for doorbell to be inactive before deallocating

2017-03-13 Thread Oscar Mateo
On 03/13/2017 04:46 AM, Chris Wilson wrote: On Fri, Mar 10, 2017 at 08:28:55AM -0800, Oscar Mateo wrote: Doorbell release flow requires that we wait for GEN8_DRB_VALID bit to go to zero after updating db_status before we call the GuC to release the doorbell. Does this fix some of the '110'

Re: [Intel-gfx] [08/11] drm/i915/guc: Wait for doorbell to be inactive before deallocating

2017-03-13 Thread Chris Wilson
On Fri, Mar 10, 2017 at 08:28:55AM -0800, Oscar Mateo wrote: > Doorbell release flow requires that we wait for GEN8_DRB_VALID bit to go > to zero after updating db_status before we call the GuC to release the > doorbell. Does this fix some of the '110' errors? -Chris -- Chris Wilson, Intel Open

[Intel-gfx] [08/11] drm/i915/guc: Wait for doorbell to be inactive before deallocating

2017-03-10 Thread Oscar Mateo
Doorbell release flow requires that we wait for GEN8_DRB_VALID bit to go to zero after updating db_status before we call the GuC to release the doorbell. Kudos to Daniele for finding this out. Cc: Joonas Lahtinen Cc: Daniele Ceraolo Spurio