Searched full:entity (Results 1 – 25 of 89) sorted by relevance
1234
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-entities.rst | 34 To query the attributes of an entity, applications set the id field of a
44 about the entity with the smallest id strictly larger than the requested
45 one ('next entity'), or the ``EINVAL`` error code if there is none.
47 Entity IDs can be non-contiguous. Applications must *not* try to
63 - Entity ID, set by the application. When the ID is or'ed with
65 the first entity with a larger ID. Do not expect that the ID will
67 do not hardcode entity IDs in an application.
72 - Entity name as an UTF-8 NULL-terminated string. This name must be unique
78 - Entity type, see :ref:`media-entity-functions` for details.
83 - Entity revision. Always zero (obsolete)
[all …]
|
| D | media-ioc-enum-links.rst | 13 MEDIA_IOC_ENUM_LINKS - Enumerate all pads and links for a given entity
34 To enumerate pads and/or links for a given entity, applications set the
35 entity field of a struct :c:type:`media_links_enum`
43 with information about the entity's pads. The array must have enough
44 room to store all the entity's pads. The number of pads can be retrieved
48 with information about the entity's outbound links. The array must have
49 enough room to store all the entity's outbound links. The number of
52 Only forward links that originate at one of the entity's source pads are
65 - ``entity``
66 - Entity id, set by the application.
[all …]
|
| D | media-types.rst | 10 .. _media-entity-functions:
50 .. flat-table:: Media entity functions
56 - Unknown entity. That generally indicates that a driver didn't
57 initialize properly the entity, which is a Kernel bug
60 - Data streaming input and/or output entity.
63 - V4L VBI streaming input or output entity
66 - V4L Software Digital Radio (SDR) streaming input or output entity
69 - DVB Digital TV streaming input or output entity
72 - Digital TV demodulator entity.
75 - MPEG Transport stream demux entity. Could be implemented on
[all …]
|
| D | media-controller-model.rst | 14 - An **entity** is a basic media hardware or software building block.
24 - A **pad** is a data connection endpoint through which an entity can
26 by an entity flows from the entity's output to one or more entity
31 pads, either on the same entity or on different entities. Data flows
35 connection between a Linux Kernel interface and an entity.
|
| D | media-ioc-g-topology.rst | 133 - Unique ID for the entity. Do not expect that the ID will
135 do not hardcode entity IDs in an application.
139 - Entity name as an UTF-8 NULL-terminated string. This name must be unique
144 - Entity main function, see :ref:`media-entity-functions` for details.
148 - Entity flags, see :ref:`media-entity-flag` for details.
226 - Unique ID for the entity where this pad belongs.
263 On interface to entity links: unique ID for the interface.
269 On interface to entity links: unique ID for the entity.
|
| /Documentation/driver-api/media/ |
| D | mc-core.rst | 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
60 instance, defined in ``include/media/media-entity.h``. The structure is usually
65 Drivers initialize entity pads by calling
78 ``include/media/media-entity.h``. Currently, only one type of interface is
90 defined in ``include/media/media-entity.h``. Each entity stores its pads in
91 a pads array managed by the entity driver. Drivers usually embed the array in
[all …]
|
| D | v4l2-dev.rst | 122 (entity field) by calling :c:func:`media_entity_pads_init`:
129 err = media_entity_pads_init(&vdev->entity, 1, pad);
134 A reference to the entity will be automatically acquired/released when the
187 the video device entity will be automatically registered with the media
307 Don't forget to cleanup the media entity associated with the video device if
311 (&vdev->entity);
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 20 and remote ("destination") rpmsg address. When an entity
24 dispatches them to the listening entity (a kernel driver).
38 and remote ("destination") rpmsg address. When an entity
42 dispatches them to the listening entity.
51 remote entity).
64 A channel is first created when an entity, whether local
88 The listening entity (or client) which communicates with a
|
| D | sysfs-class-fc | 8 an application or logical entity such as a virtual
10 entity utilizes a block device via the cgroup id.
|
| D | sysfs-bus-coresight-devices-stm | 53 coming from this trace entity.
|
| /Documentation/admin-guide/media/ |
| D | imx7.rst | 39 This is the MIPI CSI-2 receiver entity. It has one sink pad to receive the pixel
59 This entity has one sink pad that receives from the csi-mux entity and a single
113 - entity 1: csi (2 pads, 2 links)
123 - entity 4: csi capture (1 pad, 1 link)
129 - entity 10: csi-mux (3 pads, 2 links)
141 - entity 14: imx7-mipi-csis.0 (2 pads, 2 links)
151 - entity 17: ov2680 1-0036 (1 pad, 1 link)
195 - entity 1: csi (2 pads, 2 links)
205 - entity 4: csi capture (1 pad, 1 link)
211 - entity 10: ov5640 1-003c (1 pad, 1 link)
|
| D | imx.rst | 109 i.MX6Q SabreAuto. Refer to these diagrams in the entity descriptions
140 This is the MIPI CSI-2 receiver entity. It has one sink pad to receive
146 This entity actually consists of two sub-blocks. One is the MIPI CSI-2
167 MIPI CSI-2 virtual channels from imx6-mipi-csi2 entity. They have a
190 This entity has two source pads. The first source pad can link directly
191 to the ipuX_vdic entity or the ipuX_ic_prp entity, using hardware links
194 When the direct source pad is routed to the ipuX_ic_prp entity, frames
198 When the direct source pad is routed to the ipuX_vdic entity, the VDIC
200 (see description of ipuX_vdic entity).
257 sink and source pads. The ipuX_csiY entity then applies the best
[all …]
|
| D | vimc.rst | 47 Subdevices define the behavior of an entity in the topology. Depending on the
48 subdevice, the entity can have multiple pads of type source or sink.
65 - entity 28: Lens A (0 pad, 0 link)
68 - entity 29: Lens B (0 pad, 0 link)
|
| D | qcom_camss.rst | 133 source pad on a single media entity.
164 compose selection rectangle on the sink pad of the 'msm_vfe0_pix' entity.
167 crop selection rectangle on the source pad of the 'msm_vfe0_pix' entity.
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | hardware-timestamps-common.yaml | 14 hardware means to timestamp entity in realtime. The entity could be anything
|
| /Documentation/networking/ |
| D | gtp.rst | 159 Local GTP-U entity and tunnel identification
165 There is only one GTP-U entity (and therefore SGSN/GGSN/S-GW/PDN-GW
167 per GTP-U entity.
169 A specific tunnel is only defined by the destination entity. Since the
175 * when sending, the remote entity is defined by the remote IP and
179 * when receiving the local entity is defined by the local
190 GTP-U protocol entity using the same TEID value except
196 necessary that the GTP-U entity accepts traffic for TEIDs from
|
| /Documentation/userspace-api/media/ |
| D | media.h.rst.exceptions | 15 #ignore legacy entity type macros
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-routing.rst | 13 …ING - VIDIOC_SUBDEV_S_ROUTING - Get or set routing between streams of media pads in a media entity.
40 These ioctls are used to get and set the routing in a media entity.
41 The routing configuration determines the flows of data inside an entity.
|
| /Documentation/translations/zh_CN/video4linux/ |
| D | v4l2-framework.txt | 293 结构体中的 media_entity 结构体（entity 域）：
298 err = media_entity_pads_init(&sd->entity, npads, pads);
303 当（任何）子设备节点被打开/关闭，对 entity 的引用将被自动获取/释放。
307 media_entity_cleanup(&sd->entity);
600 嵌入在 video_device 结构体中的 media_entity（entity 域）结构体：
605 err = media_entity_pads_init(&vdev->entity, 1, pad);
610 当（任何）子设备节点被打开/关闭，对 entity 的引用将被自动获取/释放。
725 media_entity_cleanup(&vdev->entity);
|
| /Documentation/translations/zh_CN/ |
| D | glossary.rst | 32 * PELT: 实体负载跟踪。（Per-Entity Load Tracking）
|
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 164 entity or member of an listed entity, then the response teams can
165 request the disclosure of that expert from that entity. This ensures
166 that the expert is also part of the entity's response team.
203 If an expert is employed by or a member of an entity on the disclosure list
205 the relevant entity.
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.yaml | 14 of processors have separate hardware entity which is now responsible for the
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
|
| /Documentation/scheduler/ |
| D | schedutil.rst | 11 PELT (Per Entity Load Tracking)
36 reflects the time an entity spends on the CPU, while 'runnable' reflects the
37 time an entity spends on the runqueue. When there is only a single task these
|
| D | sched-design-CFS.rst | 175 It puts the scheduling entity (task) into the red-black tree and
181 corresponding scheduling entity out of the red-black tree. It decrements
188 entity at the right-most end of the red-black tree.
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 32 A property set is a collection of properties applicable to a hardware entity
39 to as a whole (and to be treated as a separate entity). The canonical
|
1234