Searched full:field (Results 1 – 25 of 559) sorted by relevance
12345678910>>...23
| /Documentation/media/uapi/v4l/ |
| D | field-order.rst | 13 Field Order
20 odd and even field are transmitted, and due to a small delay between
30 object on screen may well move between one field and the next. For
32 which field of a frame is older, the *temporal order*.
34 When the driver provides or accepts images field by field rather than
37 even) fields, the *spatial order*: The first line of the top field is
39 field is the second line of that frame.
42 whether a frame commences with the top or bottom field is pointless. Any
48 Counter to intuition the top field is not necessarily the older field.
49 Whether the older field contains the top or bottom lines is a convention
[all …]
|
| D | vidioc-g-dv-timings.rst | 100 formats the height of the active video in each field is
127 to the odd field (aka field 1).
131 to the odd field (aka field 1).
135 to the odd field (aka field 1).
138 - Vertical front porch in lines for the even field (aka field 2) of
139 interlaced field formats. Must be 0 for progressive formats.
142 - Vertical sync length in lines for the even field (aka field 2) of
143 interlaced field formats. Must be 0 for progressive formats.
146 - Vertical back porch in lines for the even field (aka field 2) of
147 interlaced field formats. Must be 0 for progressive formats.
[all …]
|
| D | pixfmt-v4l2.rst | 30 - Image height in pixels. If ``field`` is one of ``V4L2_FIELD_TOP``,
32 refers to the number of lines in the field, otherwise it refers to
33 the number of lines in the frame (which is twice the field height
56 - ``field``
57 - Field order, from enum :c:type:`v4l2_field`.
59 capture or output only the top or bottom field, or both fields
61 separate buffers. Drivers return the actual field order selected.
62 For more details on fields see :ref:`field-order`.
69 Both applications and drivers can set this field to request
73 implies applications can just set this field to zero to get a
[all …]
|
| D | dev-raw-vbi.rst | 48 in the ``capabilities`` field of struct
79 ``type`` field of a struct :c:type:`v4l2_format` to
86 To request different parameters applications set the ``type`` field of a
146 line of the VBI image, of the first and the second field
151 for each field for each 525 or 625 line format as a convenience.
158 - The number of lines in the first and second field image,
164 picture area, implementing a 'full field mode' to capture data
168 if no data is required from the respective field; ``count``\ [1]
171 driver. Anyway, drivers may not support single field capturing and
175 bounds depicted\ [#f4]_, or a field image covering lines of two
[all …]
|
| D | vidioc-qbuf.rst | 49 To enqueue a buffer applications set the ``type`` field of a struct
53 Applications must also set the ``index`` field. Valid index numbers
62 ``bytesused``, ``field`` and ``timestamp`` fields, see :ref:`buffer`
65 :ref:`multi-planar API <planar-apis>`, the ``m.planes`` field must
67 :c:type:`v4l2_plane` and the ``length`` field must be set
71 ``memory`` field to ``V4L2_MEMORY_MMAP``. When ``VIDIOC_QBUF`` is called
74 the ``V4L2_BUF_FLAG_DONE`` flag in the ``flags`` field, or it returns an
78 ``memory`` field to ``V4L2_MEMORY_USERPTR``, the ``m.userptr`` field to
85 ``flags`` field, or it returns an error code. This ioctl locks the
93 ``memory`` field to ``V4L2_MEMORY_DMABUF`` and the ``m.fd`` field to a
[all …]
|
| D | hist-v4l2.rst | 46 1998-10-02: The ``id`` field was removed from struct
154 type field selecting the union member as parameter. Purpose is to
168 ``VIDIOC_S_OUTPARM``. A ``type`` field in the new struct
176 introduced and one dropped. The ``catname`` field was replaced by a
177 ``group`` field.
194 until the time in the timestamp field has arrived. I would like to
207 timestamp field to a 64-bit integer, and I will change the
211 8. A ``sequence`` field was added to struct
212 :c:type:`v4l2_buffer`. The ``sequence`` field counts
221 ``reserved1`` field became ``offset``. Previously drivers were required
[all …]
|
| D | vidioc-querybuf.rst | 46 Applications set the ``type`` field of a struct
50 and the ``index`` field. Valid index numbers range from zero to the
56 field must contain a userspace pointer to an array of struct
57 :c:type:`v4l2_plane` and the ``length`` field has to be set
62 In the ``flags`` field the ``V4L2_BUF_FLAG_MAPPED``,
64 ``V4L2_BUF_FLAG_DONE`` flags will be valid. The ``memory`` field will be
67 device memory, the ``length`` field its size. For the multi-planar API,
69 elements will be used instead and the ``length`` field of struct
|
| D | vidioc-g-frequency.rst | 46 the ``tuner`` field of a struct
51 driver stores the current frequency in the ``frequency`` field.
74 the struct :c:type:`v4l2_input` ``tuner`` field and
75 the struct :c:type:`v4l2_tuner` ``index`` field, or
76 the struct :c:type:`v4l2_output` ``modulator`` field
78 field.
82 :c:type:`v4l2_tuner` ``type`` field. The type must be
84 to ``V4L2_TUNER_ANALOG_TV`` for all others. Set this field to
109 field is wrong.
|
| D | vidioc-g-fbuf.rst | 65 initialize the ``flags`` field of a struct
74 applications must initialize the ``flags`` field, the ``fmt``
115 - This field is irrelevant to *non-destructive Video Overlays*. For
141 - For *non-destructive Video Overlays* this field only defines a
143 ``chromakey`` field.
148 field. For *Video Output Overlays* the driver must return a valid
162 - ``field``
163 - Drivers and applications shall ignore this field. If applicable,
164 the field order is selected with the
165 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, using the ``field``
[all …]
|
| D | dev-overlay.rst | 38 directed away from overlay to capture, or one field may be used for
52 ``V4L2_CAP_VIDEO_OVERLAY`` flag in the ``capabilities`` field of struct
131 To get the current parameters applications set the ``type`` field of a
138 To program the overlay window applications set the ``type`` field of a
173 ``enum v4l2_field field``
174 Applications set this field to determine which video field shall be
178 field order and return the actual setting here.
182 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` applications set this field
186 field), with bytes in host order. E. g. for
193 applications can set this field to point to an array of clipping
[all …]
|
| D | vidioc-g-parm.rst | 120 the driver, in seconds. The field is intended to skip frames on
127 field). Changing the video standard (also implicitly by switching
129 period. To reset manually applications can just set this field to
133 ``V4L2_CAP_TIMEPERFRAME`` flag in the ``capability`` field.
137 applications and drivers must set this field to zero. Applications
138 using this field should check the driver name and version, see
142 - Applications set this field to the desired number of buffers used
176 The field is intended to repeat frames on the driver side in
184 field). Changing the video standard (also implicitly by switching
186 period. To reset manually applications can just set this field to
[all …]
|
| D | vidioc-s-hw-freq-seek.rst | 51 :c:type:`v4l2_tuner` ``capability`` field has the
82 :c:type:`v4l2_input` ``tuner`` field and the struct
83 :c:type:`v4l2_tuner` ``index`` field.
87 :c:type:`v4l2_tuner` ``type`` field. See
97 ``capability`` field will tell you what the hardware supports.
107 :c:type:`v4l2_tuner` ``capability`` field has the
109 struct :c:type:`v4l2_tuner` ``capability`` field has
116 :c:type:`v4l2_tuner` ``capability`` field has the
118 struct :c:type:`v4l2_tuner` ``capability`` field has
|
| D | vidioc-create-bufs.rst | 51 ``count`` field must be set to the number of requested buffers, the
52 ``memory`` field specifies the requested I/O method and the ``reserved``
55 The ``format`` field specifies the image format that the buffers must be
61 ``type`` field the requested buffer size (for single-planar) or plane
67 defined by the ``format.pix.sizeimage`` field (or the corresponding
69 field is less than the minimum required for the given format, then an
105 - Applications set this field to ``V4L2_MEMORY_MMAP``,
140 The buffer type (``format.type`` field), requested I/O method
141 (``memory``) or format (``format`` field) is not valid.
|
| D | diff-v4l.rst | 77 The ``name`` field in struct ``video_capability`` became
110 - ``V4L2_FBUF_CAP_CHROMAKEY`` in field ``capability`` of struct
116 ``V4L2_FBUF_CAP_BITMAP_CLIPPING`` in field ``capability`` of
121 - ``V4L2_FBUF_CAP_EXTERNOVERLAY`` *not set* in field ``capability``
162 The ``audios`` field was replaced by ``capabilities`` flag
186 The ``channel`` field counting inputs was renamed to ``index``, the
203 Unlike the ``tuners`` field expressing the number of tuners of this
207 associated with the input, if any, is stored in field ``tuner`` of
213 ``VIDEO_VC_AUDIO`` flag was replaced by the ``audioset`` field. V4L2
215 ``audioset`` field represents one audio input this video input combines
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | rcar-fdp1.rst | 26 - The current field is scaled vertically by averaging adjacent lines to
31 the current field. This method is also known as Field Averaging (FAV).
32 * - ``"Previous field" (4)``
33 - The current field is weaved with the previous field, i.e. the previous
34 field is used to fill missing lines from the current field. This method
36 * - ``"Next field" (5)``
37 - The current field is weaved with the next field, i.e. the next field is
38 used to fill missing lines from the current field. This method is also
|
| D | imx7.rst | 89 media-ctl -V "'ov2680 1-0036':0 [fmt:SBGGR10_1X10/800x600 field:none]"
90 media-ctl -V "'csi-mux':1 [fmt:SBGGR10_1X10/800x600 field:none]"
91 media-ctl -V "'csi-mux':2 [fmt:SBGGR10_1X10/800x600 field:none]"
92 media-ctl -V "'imx7-mipi-csis.0':0 [fmt:SBGGR10_1X10/800x600 field:none]"
93 media-ctl -V "'csi':0 [fmt:SBGGR10_1X10/800x600 field:none]"
117 … [fmt:SBGGR10_1X10/800x600 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:full-range]
120 … [fmt:SBGGR10_1X10/800x600 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:full-range]
133 [fmt:Y8_1X8/1x1 field:none]
135 [fmt:SBGGR10_1X10/800x600 field:none]
138 [fmt:SBGGR10_1X10/800x600 field:none]
[all …]
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 47 the above example, the first field of statistics would be 446216.
53 All fields except field 9 are cumulative since boot. Field 9 should
64 Field 1 -- # of reads completed
67 Field 2 -- # of reads merged, field 6 -- # of writes merged
71 as only one I/O. This field lets you know how often this was done.
73 Field 3 -- # of sectors read
76 Field 4 -- # of milliseconds spent reading
80 Field 5 -- # of writes completed
83 Field 6 -- # of writes merged
84 See the description of field 2.
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | tvp7002.txt | 24 - field-even-active: Active-high Field ID output polarity control of the bus.
25 Under normal operation, the field ID output is set to logic 1 for an odd field
26 (field 1) and set to logic 0 for an even field (field 0).
48 field-even-active = <0>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
26 NOTE: this field can be used in conjunction with microvolts
32 Some regulator directories will contain a field called
72 Each regulator directory will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
[all …]
|
| /Documentation/x86/ |
| D | boot.rst | 38 Protocol 2.04 (Kernel 2.6.14) Extend the syssize field to four bytes.
43 Protocol 2.06 (Kernel 2.6.22) Added a field that contains the size of
54 Protocol 2.09 (Kernel 2.6.26) Added a field of 64-bit physical
61 Protocol 2.11 (Kernel 3.6) Added a field for offset of EFI handover
64 Protocol 2.12 (Kernel 3.8) Added the xloadflags field and extension fields
213 (1) For backwards compatibility, if the setup_sects field contains 0, the
217 field are unusable, which means the size of a bzImage kernel
230 Otherwise, the "version" field contains the protocol version,
231 e.g. protocol version 2.01 will contain 0x0201 in this field. When
239 For each field, some are information from the kernel to the bootloader
[all …]
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.txt | 200 The ioctlfd field is a mount point file descriptor of an autofs mount
210 The path field is used to pass a path where it is needed and the size field
222 mismatch results in a -EINVAL return. If the size field is greater than
259 with the ioctlfd field set to a valid autofs mount point descriptor
260 and sets the requested version number in version field of struct args_protover
261 or sub_version field of struct args_protosubver. These commands return
270 the path field set and the size field adjusted appropriately as well
271 as the devid field of struct args_openmount set to the device number of
274 autofs_dev_ioct with the ioctlfd field set to the descriptor obtained
286 with the ioctlfd field set to the descriptor obtained from the open
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | checksums.rst | 39 - The entire superblock up to the checksum field. The UUID lives inside
43 - UUID + the entire MMP block up to the checksum field.
46 - UUID + the entire extended attribute block. The checksum field is set to
51 fake entry enclosing the checksum field.
55 The checksum field is set to zero.
59 the checksum field.
67 field is set to zero. Each inode has its own checksum.
|
| /Documentation/hid/ |
| D | hid-sensor.rst | 22 Field(2)
36 This accelerometer-3D has some fields. Here for example field 2 is motion intensity
38 order of fields and length of each field is important as the input event raw
115 A processing driver can look for some field of interest and check if it exists
118 These indexes avoid searching every time and getting field index to get or set.
126 This interface is used to set a value for a field in feature report. For example
127 if there is a field report_interval, which is parsed by a call to
129 individual field::
135 This interface is used to get a value for a field in input report. For example
136 if there is a field report_interval, which is parsed by a call to
[all …]
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 132 All <field string> description with * has the following format::
134 field: <integer>, <field string>
136 Where value of <integer> should be the position of "string" in <field
137 string> description. Otherwise, <field string> will be "unknown".
139 All <field strings> description with # has the following format::
141 field: <integer>
142 <field strings>
145 <integer>. The bit position is the position of "string" in <field
148 For more detailed explanation of every field, please refer to UEFI
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic-v3.txt | 37 - base field encodes bits [51:16] of the guest physical base address
48 by presetting the index field in the attr data.
69 The attr field of kvm_device_attr encodes two values:
92 The mpidr field is used to specify which
96 architecture defined MPIDR, and the field is encoded as follows:
157 The attr field of kvm_device_attr encodes two values:
161 The mpidr field encodes the CPU ID based on the affinity information in the
162 architecture defined MPIDR, and the field is encoded as follows:
166 The instr field encodes the system register to access based on the fields
177 CPU specified by the mpidr field.
[all …]
|
12345678910>>...23