Lines Matching refs:can

24 An entity is a basic media hardware building block. It can correspond to
30 A pad is a connection endpoint through which an entity can interact with
102 although drivers can allocate entities directly.
109 The media_entity name, type, flags, revision and group_id fields can be
111 higher-level standard structures can have some of those fields set by the
132 Entities are identified by a unique positive integer ID. Drivers can provide an
159 	This can be used to report the default audio and video devices or the
162 Logical entity groups can be defined by setting the group ID of all member
212 	MEDIA_LNK_FL_ENABLED indicates that the link is enabled and can be used
214 	one of them can be enabled at a time.
215 	MEDIA_LNK_FL_IMMUTABLE indicates that the link enabled state can't be
226 To iterate over all entities belonging to a media device, drivers can use the
236 Drivers might also need to iterate over all entities in a graph that can be
253 Drivers can then retrieve the next entity by calling
259 Graph traversal can be interrupted at any moment. No cleanup function call is
260 required and the graph structure can be freed normally.
262 Helper functions can be used to find a link between two given pads, or a pad
278 media_entity structure includes a use_count field that media drivers can use to
289 Link properties can be modified at runtime by calling
296 link. Links marked with the IMMUTABLE link flag can not be enabled or disabled.
303 Media device drivers can be notified of link setup operations by setting the
314 the link_setup operation must return -EBUSY and can't implicitly disable the
332 in higher-level pipeline structures and can then access the pipeline through
335 Calls to media_entity_pipeline_start() can be nested. The pipeline pointer must
350 a streaming entity. Links that can be modified while streaming must be marked
354 changing entities configuration parameters) drivers can explicitly check the