Lack of MTX_CMDID_NULL causes topaz fence to timeout
authorNaeem M. Afzal <naeem.m.afzal@intel.com>
Thu, 16 Feb 2012 17:04:07 +0000 (09:04 -0800)
committerMarkus Lehtonen <markus.lehtonen@linux.intel.com>
Tue, 3 Jul 2012 09:30:15 +0000 (12:30 +0300)
commitf7485a17d41da5136d9c8ca58045c8badcb877e5
tree7177fc84945c73a96b01c3bdb56fc4a0808a1f27
parent1063bb46f69337be9321e5e222b2bc139d856921
Lack of MTX_CMDID_NULL causes topaz fence to timeout

this timeout results in reset the hardware for every
jpeg frame encode. vaSyncSurface will not complete until
the timeout occurs, since it is still waiting for
MTX_CMID_NULL. This shows up as slow performance
(we have to wait for timeout).

Issue: ANDROID-1633

Signed-off-by: naeem.m.afzal@intel.com
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
drivers/staging/mrst/imgv/pnw_topaz.c