OpenMAX IL introduction

12. Trigger Event Handle
OpenMAX components
Events and Callbacks
Six kinds of events are sent by a component to the IL client • Command complete notification events are triggered upon successful execution of a command. • Error events are enumerated and can occur at any time • Marked buffer events are triggered upon detection of a marked buffer by a component. • A port settings changed notification event is generated when the component changes its port settings. • A buffer flag event is triggered when an end of stream is encountered. • A resources acquired event is generated when a component gets resources that it has been waiting for. Ports make buffer handling callbacks upon availability of a buffer or to indicate that a buffer is needed.
OpenMAX layers
OpenMAX IL domains
• OpenMAX IL components are divided in three main domains: audio, video and imaging • A support for other domains (timing info, bitstream) is provided. It is generally classified as “other” domain • The other domain includes also the mixeddomain components, like video/imaging processors
OpenMAX IL Control API
• Core APIs
– Call sequence (spec 3.2)
• Component APIs
– Call sequence (spec 3.4)
OpenMAX IL Data API
• • • • Four domains Include the parameters Types defines Extension Index
Terms
• • • • • • • • • IL client IL Core IL component Accelerated component Accelerator Host Processor Main Memory Resource manager Tunnels/Tunneling
OpenMAX IL arch
Core
• Communicate with IL client • Load all components • Setup the tunnels
OpenMAX State & Transition
Component Architecture
Communication Behavior
IL client Component Setup
• Load all tunneling components and set up • Command all tunnel componets to transition from the loaded state to the idle state

Others
• Synchronization • Rate Control • Resource Management (HW vendor-specific)
Generic Components
• Seeking Component • Clock Component
– For A-V sync – Media Clock – Wall Clock
Componet setup (con’t)
• Transition Form Loaded to Idle with buffer sharing • Transition From Loaded to Idle without buffer sharing
Port reconnection
Queues & Flush
OpenMAX | IL Introduction
Outline
• • • • • OpenMAX soft layers OpenMAX IL architecture Core & Components OpenMAX Conformance Test Application supports
Conformance test
• All defined APIs • Muti-thread test
Applications
• GStreamer-omx ?
IL client
1. Send Buffer 1 2. Send Buffer 2 3. Send Buffer 3 4. Send Buffer 4 5. Send Buffer 5 6. Flush 7. Return Buffer 1 --- buffer filled
8. Return Buffer 2 --- buffer filled 9. Return Buffer 3 --- buffer NOT filled 10. Return Buffer 4 --- buffer NOT filled 11. Return Buffer 5 --- buffer NOT filled
Tunneled Buffer Allocate
• Terms
– Supplier port/non-supplier port – allocator port – Tunneling port – Sharing port – Tunneling component
Tunneled Buffer Allocate (cont’d)