Lines Matching +full:audio +full:- +full:video
1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_QUERYCAP - Query device capabilities
47 .. flat-table:: struct v4l2_capability
48 :header-rows: 0
49 :stub-columns: 0
52 * - __u8
53 - ``driver``\ [16]
54 - Name of the driver, a unique NUL-terminated ASCII string. For
62 sure the strings are properly NUL-terminated.
63 * - __u8
64 - ``card``\ [32]
65 - Name of the device, a NUL-terminated UTF-8 string. For example:
67 models of video hardware. This information is intended for users,
73 * - __u8
74 - ``bus_info``\ [32]
75 - Location of the device in the system, a NUL-terminated ASCII
79 devices controlled by the driver ("platform:vivid-000"). The
81 Express boards, "usb-" for USB devices, "I2C:" for i2c devices,
84 * - __u32
85 - ``version``
86 - Version number of the driver.
91 example, a stable or distribution-modified kernel uses the V4L2
97 * - :cspan:`2`
106 * - __u32
107 - ``capabilities``
108 - Available capabilities of the physical device as a whole, see
109 :ref:`device-capabilities`. The same physical device can export
115 applications to open just one of the devices (typically the video
116 device) and discover whether video, vbi and/or radio are also
118 * - __u32
119 - ``device_caps``
120 - Device capabilities of the opened device, see
121 :ref:`device-capabilities`. Should contain the available
124 capabilities and no video or vbi capabilities. This field is only
129 * - __u32
130 - ``reserved``\ [3]
131 - Reserved for future extensions. Drivers must set this array to
137 .. _device-capabilities:
141 .. flat-table:: Device Capabilities Flags
142 :header-rows: 0
143 :stub-columns: 0
146 * - ``V4L2_CAP_VIDEO_CAPTURE``
147 - 0x00000001
148 - The device supports the single-planar API through the
149 :ref:`Video Capture <capture>` interface.
150 * - ``V4L2_CAP_VIDEO_CAPTURE_MPLANE``
151 - 0x00001000
152 - The device supports the :ref:`multi-planar API <planar-apis>`
153 through the :ref:`Video Capture <capture>` interface.
154 * - ``V4L2_CAP_VIDEO_OUTPUT``
155 - 0x00000002
156 - The device supports the single-planar API through the
157 :ref:`Video Output <output>` interface.
158 * - ``V4L2_CAP_VIDEO_OUTPUT_MPLANE``
159 - 0x00002000
160 - The device supports the :ref:`multi-planar API <planar-apis>`
161 through the :ref:`Video Output <output>` interface.
162 * - ``V4L2_CAP_VIDEO_M2M``
163 - 0x00008000
164 - The device supports the single-planar API through the Video
165 Memory-To-Memory interface.
166 * - ``V4L2_CAP_VIDEO_M2M_MPLANE``
167 - 0x00004000
168 - The device supports the :ref:`multi-planar API <planar-apis>`
169 through the Video Memory-To-Memory interface.
170 * - ``V4L2_CAP_VIDEO_OVERLAY``
171 - 0x00000004
172 - The device supports the :ref:`Video Overlay <overlay>`
173 interface. A video overlay device typically stores captured images
174 directly in the video memory of a graphics card, with hardware
176 * - ``V4L2_CAP_VBI_CAPTURE``
177 - 0x00000010
178 - The device supports the :ref:`Raw VBI Capture <raw-vbi>`
180 * - ``V4L2_CAP_VBI_OUTPUT``
181 - 0x00000020
182 - The device supports the :ref:`Raw VBI Output <raw-vbi>`
184 * - ``V4L2_CAP_SLICED_VBI_CAPTURE``
185 - 0x00000040
186 - The device supports the :ref:`Sliced VBI Capture <sliced>`
188 * - ``V4L2_CAP_SLICED_VBI_OUTPUT``
189 - 0x00000080
190 - The device supports the :ref:`Sliced VBI Output <sliced>`
192 * - ``V4L2_CAP_RDS_CAPTURE``
193 - 0x00000100
194 - The device supports the :ref:`RDS <rds>` capture interface.
195 * - ``V4L2_CAP_VIDEO_OUTPUT_OVERLAY``
196 - 0x00000200
197 - The device supports the :ref:`Video Output Overlay <osd>` (OSD)
198 interface. Unlike the *Video Overlay* interface, this is a
199 secondary function of video output devices and overlays an image
200 onto an outgoing video signal. When the driver sets this flag, it
203 * - ``V4L2_CAP_HW_FREQ_SEEK``
204 - 0x00000400
205 - The device supports the
208 * - ``V4L2_CAP_RDS_OUTPUT``
209 - 0x00000800
210 - The device supports the :ref:`RDS <rds>` output interface.
211 * - ``V4L2_CAP_TUNER``
212 - 0x00010000
213 - The device has some sort of tuner to receive RF-modulated video
216 * - ``V4L2_CAP_AUDIO``
217 - 0x00020000
218 - The device has audio inputs or outputs. It may or may not support
219 audio recording or playback, in PCM or compressed formats. PCM
220 audio support must be implemented as ALSA or OSS interface. For
221 more information on audio inputs and outputs see :ref:`audio`.
222 * - ``V4L2_CAP_RADIO``
223 - 0x00040000
224 - This is a radio receiver.
225 * - ``V4L2_CAP_MODULATOR``
226 - 0x00080000
227 - The device has some sort of modulator to emit RF-modulated
228 video/audio signals. For more information about modulator
230 * - ``V4L2_CAP_SDR_CAPTURE``
231 - 0x00100000
232 - The device supports the :ref:`SDR Capture <sdr>` interface.
233 * - ``V4L2_CAP_EXT_PIX_FORMAT``
234 - 0x00200000
235 - The device supports the struct
237 * - ``V4L2_CAP_SDR_OUTPUT``
238 - 0x00400000
239 - The device supports the :ref:`SDR Output <sdr>` interface.
240 * - ``V4L2_CAP_META_CAPTURE``
241 - 0x00800000
242 - The device supports the :ref:`metadata` capture interface.
243 * - ``V4L2_CAP_READWRITE``
244 - 0x01000000
245 - The device supports the :c:func:`read()` and/or
247 * - ``V4L2_CAP_STREAMING``
248 - 0x04000000
249 - The device supports the :ref:`streaming <mmap>` I/O method.
250 * - ``V4L2_CAP_META_OUTPUT``
251 - 0x08000000
252 - The device supports the :ref:`metadata` output interface.
253 * - ``V4L2_CAP_TOUCH``
254 - 0x10000000
255 - This is a touch device.
256 * - ``V4L2_CAP_IO_MC``
257 - 0x20000000
258 - There is only one input and/or output seen from userspace. The whole
259 video topology configuration, including which I/O entity is routed to
262 * - ``V4L2_CAP_DEVICE_CAPS``
263 - 0x80000000
264 - The driver fills the ``device_caps`` field. This capability can
271 On success 0 is returned, on error -1 and the ``errno`` variable is set
273 :ref:`Generic Error Codes <gen-errors>` chapter.