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