LibVA Protected Content API

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>
10 files changed
tree: 043fe7eb985dda0380af3eb7fdee4d6f77b9f78a
  1. .github/
  2. build/
  3. doc/
  4. pkgconfig/
  5. va/
  6. .cvsignore
  7. .gitignore
  8. .travis.yml
  9. Android.mk
  10. autogen.sh
  11. configure.ac
  12. CONTRIBUTING.md
  13. COPYING
  14. Makefile.am
  15. meson.build
  16. meson_options.txt
  17. NEWS
  18. README.md
  19. style_unify
README.md

Stories in Ready Build Status Coverity Scan Build Status

Libva Project

Libva is an implementation for VA-API (Video Acceleration API)

VA-API is an open-source library and API specification, which provides access to graphics hardware acceleration capabilities for video processing. It consists of a main library and driver-specific acceleration backends for each supported hardware vendor.

If you would like to contribute to libva, check our Contributing guide.

We also recommend taking a look at the ‘janitorial’ bugs in our list of open issues as these bugs can be solved without an extensive knowledge of libva.

We would love to help you start contributing!

Doxygen files are regularly updated through Github Pages and can be accessed directly through github pages libva

The libva development team can be reached via our mailing list and on IRC in channel ##intel-media on Freenode.

We also use #Slack and host VAAPI Media Slack Team. You can signup by submitting your email address to our Slack Team invite page.

Slack complements our other means of communication. Pick the one that works best for you!