Lines Matching full:by
28 other entities. Data (not restricted to video) produced by an entity
39 A media device is represented by a struct media_device
41 Allocation of the structure is handled by the media device driver, usually by
45 Drivers initialise media device instances by calling
47 registered by calling :c:func:`__media_device_register()` via the macro
48 ``media_device_register()`` and unregistered by calling
50 eventually cleaned up by calling :c:func:`media_device_cleanup()`.
59 Entities are represented by a struct media_entity
65 Drivers initialize entity pads by calling
68 Drivers register entities with a media device by calling
70 and unregistered by calling
76 Interfaces are represented by a
79 defined: a device node. Such interfaces are represented by a
82 Drivers initialize and create device node interfaces by calling
84 and remove them by calling:
89 Pads are represented by a struct media_pad instance,
91 a pads array managed by the entity driver. Drivers usually embed the array in
94 Pads are identified by their entity and their 0-based index in the pads
114 Links are represented by a struct media_link instance,
124 Drivers create pad to pad links by calling:
132 Drivers create interface to entity links by calling:
169 supported by the graph traversal API. To prevent infinite loops, the graph
173 Drivers initiate a graph traversal by calling
176 The graph structure, provided by the caller, is initialized to start graph
179 Drivers can then retrieve the next entity by calling
203 The :c:type:`media_entity<media_entity>`.\ ``use_count`` field is owned by
205 touched by entity drivers. Access to the field must be protected by the
211 Link properties can be modified at runtime by calling
219 towards the final sinks. The stream can be modified on the route by the
224 interdependency can be caused by the hardware (e.g. configuration of a second
225 stream cannot be changed if the first stream has been enabled) or by the driver
230 prevent link states from being modified during streaming by calling
235 The struct media_pipeline instance pointed to by
246 it will clean up any of the changes it did by itself.
257 Link configuration will fail with ``-EBUSY`` by default if either end of the
269 Link validation is performed by :c:func:`media_pipeline_start()`
277 Subsystems should facilitate link validation by providing subsystem specific
315 handled by the kref put handler.