Lines Matching refs:entity

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
31 other entities. Data (not restricted to video) produced by an entity
32 flows from the entity's output to one or more entity inputs. Pads should
36 on the same entity or on different entities. Data flows from a source
100 include/media/media-entity.h. The structure is usually embedded into a
106 	media_entity_init(struct media_entity *entity, u16 num_pads,
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
130 				     struct media_entity *entity);
140 	media_device_unregister_entity(struct media_entity *entity);
142 Unregistering an entity will not change the IDs of the other entities, and the
143 ID will never be reused for a newly registered entity.
148 Drivers free resources associated with an entity by calling
150 	media_entity_cleanup(struct media_entity *entity);
153 entity. Note that the media_entity instance itself must be freed explicitly by
156 Entities have flags that describe the entity capabilities and state.
158 	MEDIA_ENT_FL_DEFAULT indicates the default entity for a given type.
162 Logical entity groups can be defined by setting the group ID of all member
163 entities to the same non-zero value. An entity group serves no purpose in the
165 field belongs to the media device driver and must not by touched by entity
177 include/media/media-entity.h. Each entity stores its pads in a pads array
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.
196 include/media/media-entity.h. Each entity stores all links originating at or
198 twice, once in the source entity and once in the target entity. The array is
207 An entry in the link array of each entity is allocated and stores pointers
229 	struct media_entity *entity;
231 	media_device_for_each_entity(entity, mdev) {
232 		/* entity will point to each entity in turn */
237 reached only through enabled links starting at a given entity. The media
248 				      struct media_entity *entity);
251 traversal at the given entity.
253 Drivers can then retrieve the next entity by calling
279 track the number of users of every entity for power management needs.
281 The use_count field is owned by media drivers and must not be touched by entity
301 made on the first entity to restore the original link flags.
324 	media_entity_pipeline_start(struct media_entity *entity,
327 The function will mark all entities connected to the given entity through
331 every entity in the pipeline. Drivers should embed the media_pipeline structure
343 	media_entity_pipeline_stop(struct media_entity *entity);
350 a streaming entity. Links that can be modified while streaming must be marked
355 media_entity stream_count field to find out if an entity is streaming. This
363 entity which has sink pads in the pipeline. The
365 link_validate() callback, entity driver should check that the properties of
366 the source pad of the connected entity and its own sink pad match. It is up
367 to the type of the entity (and in the end, the properties of the hardware)