On Tue, Jan 22, 2013 at 02:12:17PM +0200, Mika Kuoppala wrote: > When machine was rebooted or module was reloaded, > gem_hw_init() set last_seqno to be identical to next_seqno. > This lead to situation that waits for first ever request > always passed immediately regardless if it was actually > executed. > > Use gem_set_seqno() to be consistent how hw is > initialized on init, wrap and on resume. Nice catch, and you caught the only other side-effect I could spot of moving the seqno init, so Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk> -Chris -- Chris Wilson, Intel Open Source Technology Centre
