On 04/05/18 22:06, Ezequiel Garcia wrote:
> From: Gustavo Padovan
>
> In preparation to have full support to explicit fence we are
> marking codec as non-ordered preventively. It is easier and safer from an
> uAPI point of view to move from unordered to ordered
On 04/05/18 22:06, Ezequiel Garcia wrote:
> From: Gustavo Padovan
>
> In preparation to have full support to explicit fence we are
> marking codec as non-ordered preventively. It is easier and safer from an
> uAPI point of view to move from unordered to ordered than the opposite.
>
> v3: set
From: Gustavo Padovan
In preparation to have full support to explicit fence we are
marking codec as non-ordered preventively. It is easier and safer from an
uAPI point of view to move from unordered to ordered than the opposite.
v3: set property instead of
From: Gustavo Padovan
In preparation to have full support to explicit fence we are
marking codec as non-ordered preventively. It is easier and safer from an
uAPI point of view to move from unordered to ordered than the opposite.
v3: set property instead of callback
v2: mark only codec drivers
4 matches
Mail list logo