Skip to content

Conversation

dmitryermilov
Copy link
Contributor

Fixes #397

Signed-off-by: Dmitry Ermilov dmitry.ermilov@intel.com

@dmitryermilov
Copy link
Contributor Author

@XinfengZhang , @dmitryermilov , do you have any other suggestions ?

Copy link
Contributor

@xhaihao xhaihao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dmitryermilov
Copy link
Contributor Author

@dvrogozh , @xhaihao , @XinfengZhang , @dmitry-gurulev , @wyc55069407,

Please give your input: do we need VA_TIMEOUT_INFINITE here?

@wyc55069407
Copy link

@dvrogozh , @xhaihao , @XinfengZhang , @dmitry-gurulev , @wyc55069407,

Please give your input: do we need VA_TIMEOUT_INFINITE here?

I think VA_TIMEOUT_INFINITE can be defined as max(uint64_t) or uint64_t(-1) at va.h. And add comments in the new libva interface to show this value is specific to infinite.
(Like #define VA_TIMEOUT_INFINITE (0xffffffffffffffff))

When you updated va.h. i'll update intel/media-driver#943 & intel/media-driver#945

Fixes intel#397

Signed-off-by: Dmitry Ermilov <dmitry.ermilov@intel.com>
VAStatus vaSyncSurface2 (
VADisplay dpy,
VASurfaceID surface,
uint64_t timeout_ns
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we care about infinite wait? maybe int64_t is more suitable, negative value mean infinite?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[enhance] Adding timeout for vaSyncSurface
5 participants