|
| 1 | +.. _mpp_layer_overview: |
| 2 | + |
| 3 | +Media Processing Pipelines Overview |
| 4 | +################################### |
| 5 | + |
| 6 | +The Media Processing Pipelines (MPP) layer role is to enable SOF specific use |
| 7 | +cases that are not supported directly by Zephyr. The MPP is responsible for host |
| 8 | +communication, tasks scheduling, pipeline and component management. |
| 9 | + |
| 10 | +.. uml:: images/mpp_layer_diagram.pu |
| 11 | + :caption: Media Processing Pipelines Layer diagram |
| 12 | + |
| 13 | +Services in Media Processing Pipelines Layer |
| 14 | +******************************************** |
| 15 | + |
| 16 | +Gateways |
| 17 | +======== |
| 18 | + |
| 19 | +The gateways are a key element in SOF data exchange with host, external audio |
| 20 | +peripherals and internally between firmware components. They serve as an |
| 21 | +abstraction layer for multiple data protocols. |
| 22 | + |
| 23 | +The typical audio stream (chain of pipelines) starts and ends with I/O gateway. |
| 24 | +I/O gateway represents a sink or a source interface that can be read or written |
| 25 | +via DMA operations on I/O FIFO (i.e. DMIC, SNDW, etc.) or directly via memory |
| 26 | +operations (i.e. memory buffers of IPC Gateway). Host Gateway is unique as it |
| 27 | +exposes interface endpoint to the Host driver. |
| 28 | + |
| 29 | +The stream audio gateways are created as a part of Copier component |
| 30 | +configuration. |
| 31 | + |
| 32 | +.. TODO: Add link to Copier detailed description |
| 33 | +
|
| 34 | +Examples of gateways: |
| 35 | + |
| 36 | +- DMIC Gateway, |
| 37 | +- SoundWire Gateway, |
| 38 | +- I2S Gateway, |
| 39 | +- HD/A Gateway, |
| 40 | +- IPC Gateway, |
| 41 | + |
| 42 | +.. TODO: Add link to Gateways detailed specification. |
| 43 | +
|
| 44 | +*NOTE:* Not all I/O gateways must be available in all configurations. |
| 45 | + |
| 46 | +Pipeline Management |
| 47 | +=================== |
| 48 | + |
| 49 | +The Pipeline Management is a host IPC driven service that is used to: |
| 50 | + |
| 51 | +- create / delete pipeline |
| 52 | +- switch pipeline state |
| 53 | +- create pipeline processing tasks |
| 54 | +- allocate pipeline buffers memory |
| 55 | + |
| 56 | +.. TODO: Add link to Pipeline Management IPC interface. |
| 57 | +
|
| 58 | +Processing Component Management |
| 59 | +=============================== |
| 60 | + |
| 61 | +Processing Component Management is driven by host IPC requests. It is used to: |
| 62 | + |
| 63 | +- instantiate / delete components |
| 64 | +- configure components |
| 65 | +- bind / unbind components into processing paths |
| 66 | +- load components into ADSP memory |
| 67 | + |
| 68 | +.. TODO: Add link to Component Management IPC interface. |
| 69 | +
|
| 70 | +Asynchronous Messaging |
| 71 | +====================== |
| 72 | + |
| 73 | +Asynchronous Messaging Service (AMS) provides functionality to: |
| 74 | + |
| 75 | +- send asynchronous messages to firmware components or host, |
| 76 | +- broadcast messages to multiple consumers, |
| 77 | +- asynchronous message exchange between components running on different cores |
| 78 | + |
| 79 | +.. TODO: Add link to Asynchronous Messaging Service detailed description |
| 80 | +
|
| 81 | +MPP Scheduling |
| 82 | +============== |
| 83 | + |
| 84 | +MPP Scheduling is dedicated to support Media Processing Pipelines services tasks |
| 85 | +scheduling. It exposes SOF specific interface that is implemented on top of |
| 86 | +Zephyr scheduling API. |
| 87 | + |
| 88 | +MPP Scheduling features: |
| 89 | + |
| 90 | +- Low Latency tasks scheduling, |
| 91 | +- Data Processing tasks scheduling, |
| 92 | +- Tasks with budget scheduling |
| 93 | + |
| 94 | +.. TODO: Add link to MPP Scheduling detailed description |
0 commit comments