Lines Matching full:api
2 ALSA Compress-Offload API
12 Since its early days, the ALSA API was defined with PCM support or
15 extend the existing API to compressed data streams.
22 mostly because of a lack of a generic API available in the mainline
25 Rather than requiring a compatibility break with an API change of the
26 ALSA PCM interface, a new 'Compressed Data' API is introduced to
29 The design of this API was inspired by the 2-year experience with the
31 API in the mainline kernel instead of the staging tree and make it
54 - Focus on main formats. This API provides support for the most
62 cycles. The new API needs to provide a generic way of listing these
65 - Rendering/Grabbing only. This API does not provide any means of
67 user-space for additional processing. This API focuses instead on
73 API assumes the existence of a platform-specific compatibility layer
76 applications are not supposed to make use of this API.
81 The new API shares a number of concepts with the PCM API for flow
86 borrowed from the ALSA PCM API. However, only sizes in bytes can be
94 The Compressed Data API does not make any assumptions on how the data
289 API. Support for dynamic bit-rate changes would require a tight
296 - Volume control/routing is not handled by this API. Devices exposing a
311 - Audio policy/resource management. This API does not provide any
323 - Mark Brown and Liam Girdwood for discussions on the need for this API
324 - Harsha Priya for her work on intel_sst compressed API