• Laurent Pinchart's avatar
    [media] media: Pipelines and media streams · e02188c9
    Laurent Pinchart authored
    Drivers often need to associate pipeline objects to entities, and to
    take stream state into account when configuring entities and links. The
    pipeline API helps drivers manage that information.
    
    When starting streaming, drivers call media_entity_pipeline_start(). The
    function marks all entities connected to the given entity through
    enabled links, either directly or indirectly, as streaming. Similarly,
    when stopping the stream, drivers call media_entity_pipeline_stop().
    
    The media_entity_pipeline_start() function takes a pointer to a media
    pipeline and stores it in every entity in the graph. Drivers should
    embed the media_pipeline structure in higher-level pipeline structures
    and can then access the pipeline through the media_entity structure.
    
    Link configuration will fail with -EBUSY by default if either end of the
    link is a streaming entity, unless the link is marked with the
    MEDIA_LNK_FL_DYNAMIC flag.
    Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart@ideasonboard.com>
    Acked-by: default avatarHans Verkuil <hverkuil@xs4all.nl>
    Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
    e02188c9
media-ioc-setup-link.xml 2.98 KB