driver-api/media/mc-core.rst

1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------
11 on the kernel-side implementation of the media framework.
24 in a System-on-Chip image processing pipeline), DMA channels or physical
32 A link is a point-to-point oriented connection between two pads, either
40 instance, defined in ``include/media/media-device.h``.
42 embedding the :c:type:`media_device` instance in a larger driver-specific
60 instance, defined in ``include/media/media-entity.h``. The structure is usually
61 embedded into a higher-level structure, such as
78 ``include/media/media-entity.h``. Currently, only one type of interface is
90 defined in ``include/media/media-entity.h``. Each entity stores its pads in
92 a driver-specific structure.
94 Pads are identified by their entity and their 0-based index in the pads
115 defined in ``include/media/media-entity.h``. There are two types of links:
151 ``include/media/media-device.h``.
153 ..  code-block:: c
164 framework provides a depth-first graph traversal API for that purpose.
218 source devices (such as a sensors) and flowing through media entity pads
237 media_pipeline in higher-level pipeline structures and can then access the
255 Link configuration will fail with ``-EBUSY`` by default if either end of the
277 in the end provide a way to use driver-specific callbacks.
299 Drivers should use the appropriate media-core routines to manage the shared
300 media device life-time handling the two states:
301 1. allocate -> register -> delete
302 2. get reference to already registered device -> delete
312 Call :c:func:`media_device_delete()` to free the media_device. Freeing is
318 .. kernel-doc:: include/media/media-device.h
320 .. kernel-doc:: include/media/media-devnode.h
322 .. kernel-doc:: include/media/media-entity.h
324 .. kernel-doc:: include/media/media-request.h
326 .. kernel-doc:: include/media/media-dev-allocator.h