should not create correlation buffer if the feature is not supported

[XinfengZhang]

test CreateBuffer/VAAPICreateBuffer.CreateBufferWithOutData/59
it will create VAMacroblockParameterBufferType buffer, but if driver dose not support macroblock parameter, it should return failed instead of VA_STATUS_SUCCESS

[XinfengZhang]

also VAQMatrixBufferType in "CreateBuffer/VAAPICreateBuffer.CreateBufferWithOutData/61 - 63"

[uartie]

@XinfengZhang how do clients/apps detect if driver supports these buffer types or not? Are there specific VA APIs that relay this information?

[XinfengZhang]

no vaapi to export the information, but we should not expect all buffer type can be created. so return unsupport error should also be acceptable.

[uartie]

Is there a set of buffer types that we know are "required" to be supported by all drivers if codec is supported? I don't know if it's a good idea to just accept unsupported as a valid result for just any/every buffer type. @xhaihao any comment?

[XinfengZhang]

@xhaihao any comments?

[xhaihao]

I agree the driver may return VA_STATUS_ERROR_UNSUPPORTED_BUFFERTYPE if the type is not supported for a given profile/entrypoint pair. In addition the doc should have a clear requirement on the required buffer type for each profile/entrypoint pair. We may update the doc in the future release.