va/buffer: Changing the usage to PIPE_MAP_DIRECTLY
Issue: Buffer is not completely derived resulting into incomplete frame.
Root Cause:
When using vaDeriveImage, the vlVaMapBuffer uses the path under
buf->derived_surface.resource
. In this the buffer is mapped with usage
flag PIPE_MAP_WRITE. The buffer fetched is incomplete or overwritten
resulting into wrong data.
Fix: When the buffer is mapped using PIPE_MAP_DIRECTLY the data was proper and no more improper frames is observed. Verified using a decode_test app.
Signed-off-by: Krunal Patel krunalkumarmukeshkumar.patel@amd.corp-partner.google.com