Lines Matching full:entity

21 An entity is a basic media hardware building block. It can correspond to
27 A pad is a connection endpoint through which an entity can interact with
28 other entities. Data (not restricted to video) produced by an entity
29 flows from the entity's output to one or more entity inputs. Pads should
33 on the same entity or on different entities. Data flows from a source
53 instance, defined in ``include/media/media-entity.h``. The structure is usually
58 Drivers initialize entity pads by calling
71 ``include/media/media-entity.h``. Currently, only one type of interface is
83 defined in ``include/media/media-entity.h``. Each entity stores its pads in
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
108 defined in ``include/media/media-entity.h``. There are two types of links:
112 Associate two entities via their PADs. Each entity has a list that points
114 A given link is thus stored twice, once in the source entity and once in
115 the target entity.
121 **2. interface to entity links**:
125 Drivers create interface to entity links by calling:
148     struct media_entity *entity;
150     media_device_for_each_entity(entity, mdev) {
151     // entity will point to each entity in turn
156 reached only through enabled links starting at a given entity. The media
170 traversal at the given entity.
172 Drivers can then retrieve the next entity by calling
192 can use to track the number of users of every entity for power management
197 touched by entity drivers. Access to the field must be protected by the
213 The function will mark all entities connected to the given entity through
217 the pipe argument will be stored in every entity in the pipeline.
239 link is a streaming entity. Links that can be modified while streaming must
244 media_entity stream_count field to find out if an entity is streaming. This
251 for any entity which has sink pads in the pipeline. The
253 purpose. In ``link_validate()`` callback, entity driver should check
254 that the properties of the source pad of the connected entity and its own
255 sink pad match. It is up to the type of the entity (and in the end, the
305 .. kernel-doc:: include/media/media-entity.h