hardware-intel-libva

Fork

h264encode: use frame height not the height from VAImage which may be wrong

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>

h264encode: correct negative POC after a new IDR

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>

h264encode: fix encode corruption issue with multiple IDR (-idr_period XX)

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>

h264encode: add some comments

Signed-off-by: Elaine Wang <elaine.wang@intel.com>

h264encode: refine calculation logic of reference frame setting

Signed-off-by: Elaine Wang <elaine.wang@intel.com>

h264encode: fix wrong print information

Signed-off-by: Elaine Wang <elaine.wang@intel.com>

AVCENC: Pass the H264 RefPicList0/1 by using slice_param instead of hacked DPB reference

Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
(cherry picked from commit 968a9bf006679ad8d752fa1ddcd4bb80fc8c5e51)

Fix possible memory leak

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
(cherry picked from commit 0b07495fc24646b47952b8df7d4e6d2df2a0f72c)

va.c: need to check the symbol before calling it

This is to fix Klockwork critical issue

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 40e5e45edf97049137bca014575607b52d3bca78)

va: fix vaErrorStr() to support new error codes.
(cherry picked from commit 7b5c35273dc0e8e0e86cf40cf2a398119a766397)

va_x11: fix klockscan issue (details is bellow)

File: va_x11.c
Function: va_DisplayContextGetDriverName -> va_DRI2GetDriverName -> dri2_util.c:isDRI2Connected
Line: 154 -> 84 -> dri2_util.c:184
Code:
TRACEBACK
va_x11.c:151: driver_name is NULL
va_x11.c:154: 'driver_name' is passed to function 'va_DRI2GetDriverName'.
dri2_util.c:84: 'driver_name' is passed to function 'isDRI2Connected'.
dri2_util.c:184: 'driver_name' is explicitly dereferenced.

Signed-off-by: Austin Yuan <shengquan.yuan@gmail.com>
(cherry picked from commit c87699f32c6c79905a2fd8675cd19f22e1f4b024)

vatrace: print target_percentage

Change-Id: I220b2fa7ad6907ab0ebda3671baeeab7fa36cc00
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 82e7dc8280da22c88a28f0a4d429f28fd99f9ced)

vatrace: trace coded buffer create/destroy

Change-Id: If0388cd5e2e141184d88ff5de5612d15e51e3d20
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 880c916092c6d68096c95e49405714d8a21f9322)

vatrace: dump unknonw private misc parameters

Change-Id: I33bbed3a1d3f297297687197f623d6c08ee8eba9
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit df5bfb6c6f248c0bcf6f2f9a74e9ffba4b0acf15)

vatrace: remove the delimiter of every elements dump

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 132f22ae9b42b4657361c87b5c7d5b14a26a52a9)

vatrace: refine the format of buf data dump

Signed-off-by: Elaine Wang <elaine.wang@intel.com>
(cherry picked from commit 2292299fe00036eb6055a84846f63f36cbae27d9)

vatrace: refine VAEncPackedHeaderParameterBufferType format

Change-Id: I1794a9c09a88b61d7abce970d7cb9a8f101162c6
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 4853e4a3a6cc5218e032a19d729096862db82bc6)

vatrace: print VAEncPackedHeaderParameterBufferType

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 82ffa4b5bfb6cf59e90eedadbdfe3efdaced35e0)

libva: Add VABuffer dumping for JPEG parameters

BZ: 98966

Dump VABuffer of JPEG parameters in libva

Change-Id: I87450d92db402a4730e0c0433215c857bc5b494d
Signed-off-by: Cheng Yao <yao.cheng@intel.com>
(cherry picked from commit 40ffef8d1fcbbc709472dc1342d7e3e983ae5d96)

vatrace: only print info of valid reference frames

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 67c489f323188df1370f8ba2d4063bc86153cce7)

vatrace: dump flags of VAPictureH264

Signed-off-by: Elaine Wang <elaine.wang@intel.com>
(cherry picked from commit e1d86f000749d5fdbd6e36b55260d3fae096e457)

LIBVA_DRIVER_NAME still needs va_getDriverName to open DRM device

va_getDriverName is bypassed when LIBVA_DRIVER_NAME is set, but driver
needs DRM device fd which is only opened in va_getDriverName

Change-Id: I4fe11edf9d8c328806255d4c93313cf99655a91d
Signed-off-by: Fei Jiang <fei.jiang@intel.com>
(cherry picked from commit 04706eb13ae410b53b6b38150413d544b7fdb524)

va_trace: refine the log format

Signed-off-by: Elaine Wang <elaine.wang@intel.com>
(cherry picked from commit 15a0fca64456d8c7de1f7aca2cb747c4929690cd)

vatrace: print function name for vaMapBuffer trace with coded buffer

also fall into default va_TraceVABuffers if the buffer type falls into
"default"

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit acbf7d0c4830763e7c3be0e71c9da972f1aea7a5)

vatrace: buffer_type_to_string: add missing VABufferType

sync with VABufferType in va/va.h.

Signed-off-by: Adrian Marius Negreanu <adrian.m.negreanu@intel.com>
(cherry picked from commit d5160173f9dd5a37c793518d1d483b09d278d90c)
[Remove unsupported types on master]
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

va_parseConfig: still need to check env_value

env_value may be NULL which means the caller doens't
care the value of the environment variable, just check
if it is set.

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 2e11d2273b2974a7d1959cbcaf8db5b8e9aedd9e)

vatrace: fix build issue

Change-Id: I1727528df6aaf48209774bada5cf136cfa1e4ee3
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 1e0421f5ce01790e700940310aafb05e4c18d8f0)

va_trace: dump basic_unit_size/rc_flags in RateControl data struct

Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
(cherry picked from commit 4a78cb4e4a2d0e5c9231c7f532d2a733cf3bfce3)

vatrace: Fix encoded coded buffer dump function

libva trace can't dump coded buffer. It's caused by the wrong
decison in vaTraceEndPicture function which only dump coded buffer
when surface dumping is enabled.
Signed-off-by: Elaine Wang <elaine.wang@intel.com>

Change-Id: I8b0ec01e59faff3bfd5345d95cbf0e781f6f3706
(cherry picked from commit 202385430f29b3d3d356d86888a0f3979986b4e7)

vatrace: fix vatrace crash during video recording

Video recording crash when va trace is enabled. It's caused by
using wrong buffer type to trace slice buffer. This patch distinguish buffer
type VAEncSliceParameterBuffer from VAEncSliceParameterBufferH264 by
the buffer size.
Signed-off-by: Elaine Wang <elaine.wang@intel.com>

Change-Id: Ibc5c6a17b155e305151a25580b4e613702665ad1
(cherry picked from commit b5b1933f60dfec8cf2cff19082362accbe6fce1d)