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 register media device instances by calling
47 and unregistered by calling :c:func:`media_device_unregister()`.
52 Entities are represented by a struct media_entity
58 Drivers initialize entity pads by calling
61 Drivers register entities with a media device by calling
63 and unregistered by calling
69 Interfaces are represented by a
72 defined: a device node. Such interfaces are represented by a
75 Drivers initialize and create device node interfaces by calling
77 and remove them by calling:
82 Pads are represented by a struct media_pad instance,
84 a pads array managed by the entity driver. Drivers usually embed the array in
87 Pads are identified by their entity and their 0-based index in the pads
107 Links are represented by a struct media_link instance,
117 Drivers create pad to pad links by calling:
125 Drivers create interface to entity links by calling:
162 supported by the graph traversal API. To prevent infinite loops, the graph
166 Drivers initiate a graph traversal by calling
169 The graph structure, provided by the caller, is initialized to start graph
172 Drivers can then retrieve the next entity by calling
195 The :c:type:`media_entity<media_entity>`.\ ``use_count`` field is owned by
197 touched by entity drivers. Access to the field must be protected by the
203 Link properties can be modified at runtime by calling
210 prevent link states from being modified during streaming by calling
216 The struct media_pipeline instance pointed to by
227 it will clean up any of the changes it did by itself.
238 Link configuration will fail with ``-EBUSY`` by default if either end of the
250 Link validation is performed by :c:func:`media_pipeline_start()`
258 Subsystems should facilitate link validation by providing subsystem specific
296 handled by the kref put handler.