Signed-off-by: Carl Zhang <carl.zhang@intel.com>

Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>

Signed-off-by: zefuli <zefu.li@intel.com>

When the parent compositor is running with a render node, Mesa will send
the render node path via wl_drm instead of the primary path. DRM
authentication doesn't work with render nodes.

This patch makes the Wayland logic consistent with the DRM logic [1].

Tested using Sway running with wlroots' headless backend.

[1]: https://github.com/intel/libva/blob/b4d0af7f43f0ef2d51f070c75429c0d6acca663b/va/drm/va_drm.c#L68

Signed-off-by: Simon Ser <contact@emersion.fr>

Dumping the real element data for IQ matrix rather than the
useless matrix pointer's address.

superres_scale_denominator value was only reflecting range [9..16] which
doesn't match the range mentioned in spec [8..16]. This commit clarifies
that when use_superres=1, superres_scale_denominator value range is
[9..16] otherwise, it is 8.

Signed-off-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>

This change will allow faster verifications of fixes in workload
.yml files since only affected workloads will actually run.

Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>

Cache needs to be up to date to avoid packages installation failures.

Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>

The Protected content APIs provide a generic mechanism for protected session
management with various assets in system such as Trusted Execution
Environment(TEE), GPU, Display. The protected session management includes
create, destroy, attach/detach, and execute according to contract with TEE,
GPU, and Display. The behavior of protected session APIs depend on
parameterization/configuration of protected sessions according to usage cases
such as TEE Communication Tools, Hardware Digital Rights Management(HWDRM) etc.

The Protected Content APIs play following roles - In TEE Communication Tools,
the APIs manifest as TEE client to honor TEE contract; In HWDRM, APIs manifest
as TEE/GPU/Display client to honor HWDRM contract.

The Protected Content APIs execute following workloads - In TEE Communication
Tools, the APIs provide infrastructure to execute TEE workloads such as TEE
capability discovery, versioning, provisioning etc.; In HWDRM, the APIs provide
infrastructure to execute HWDRM playback workloads such as license acquisition,
HW acceleration e.g. decryption/decoding of protected video/audio contents,
protected content display etc.

Signed-off-by: Gaurav Kumar <kumar.gaurav@intel.com>
Signed-off-by: Ryan T Huang <ryan.t.huang@intel.com>

Signed-off-by: Ryan T Huang <ryan.t.huang@intel.com>

There is no restriction of tile_rows and tile_cols value in AV1 spec so,
this commit excludes the commit which mentions value of tile_rows and
tile_cols to be power of 2.

Signed-off-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>

AV1 does not have any frame resolution restrictions. However, the comment
"value may not be multiple of 8" was confusing so, I am excluding it to be
in sync with the AV1 spec.

Signed-off-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>

dash and pdksh don't support $'...'

/bin/sed: -e expression #1, char 2: unknown command: `1'

already enable github actions

Signed-off-by: Carl Zhang <carl.zhang@intel.com>

freebsd-vm@v0.0.7 uses FreeBSD 12.1 which has reached EOL on 2021-01-31.
FreeBSD Project doesn't keep old packages for /latest and /quarterly.
Once 12.2 packages are built there would be none for 12.1 except for
/release_1 which is more than 1 year old.

Application needs to make sure all the entries point to valid frames
except for the intra frames (intra and key frames together are intra
frames). Because the document was only suggesting key frames, this edit
is needed. Minor edit is made to ref_frame_idx[] document to reflect
correct index values.

Signed-off-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>

The docs seem to refer to the legacy getSurfaceAttributes behavior.
Update them for the new querySurfaceAttributes behavior which
completely ignores what the user provides in the attributes array.
While at it, also document its usage with createSurfaces.

Signed-off-by: Carl Zhang <carl.zhang@intel.com>

Signed-off-by: Carl Zhang <carl.zhang@intel.com>