Lines Matching refs:by

31 other entities. Data (not restricted to video) produced by an entity
43 A media device is represented by a struct media_device instance, defined in
44 include/media/media-device.h. Allocation of the structure is handled by the
45 media device driver, usually by embedding the media_device instance in a
48 Drivers register media device instances by calling
69    "PCI:" (or "PCIe:") followed by the value of pci_name(). For USB devices,
70    the usb_make_path() function must be used. This field is used by
87 Drivers unregister media device instances by calling
99 Entities are represented by a struct media_entity instance, defined in
104 Drivers initialize entities by calling
111 higher-level standard structures can have some of those fields set by the
115 dynamically but is managed by the entity driver. Most drivers will embed the
122 advance by the entity driver. As an initial estimate, media_entity_init
127 Drivers register entities with a media device by calling
132 Entities are identified by a unique positive integer ID. Drivers can provide an
133 ID by filling the media_entity id field prior to registration, or request the
136 contiguous even when they are all assigned automatically by the framework.
138 Drivers unregister entities by calling
148 Drivers free resources associated with an entity by calling
153 entity. Note that the media_entity instance itself must be freed explicitly by
162 Logical entity groups can be defined by setting the group ID of all member
165 field belongs to the media device driver and must not by touched by entity
176 Pads are represented by a struct media_pad instance, defined in
178 managed by the entity driver. Drivers usually embed the array in a
181 Pads are identified by their entity and their 0-based index in the pads array.
195 Links are represented by a struct media_link instance, defined in
201 Drivers create links by calling
241 supported by the graph traversal API. To prevent infinite loops, the graph
245 Drivers initiate a graph traversal by calling
250 The graph structure, provided by the caller, is initialized to start graph
253 Drivers can then retrieve the next entity by calling
281 The use_count field is owned by media drivers and must not be touched by entity
282 drivers. Access to the field must be protected by the media device graph_mutex
289 Link properties can be modified at runtime by calling
303 Media device drivers can be notified of link setup operations by setting the
322 prevent link states from being modified during streaming by calling
330 The media_pipeline instance pointed to by the pipe argument will be stored in
339 clean up any of the changes it did by itself.
349 Link configuration will fail with -EBUSY by default if either end of the link is
362 Link validation is performed by media_entity_pipeline_start() for any
370 Subsystems should facilitate link validation by providing subsystem specific