~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/userspace-api/media/v4l/querycap.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/userspace-api/media/v4l/querycap.rst (Architecture ppc) and /Documentation/userspace-api/media/v4l/querycap.rst (Architecture i386)


  1 .. SPDX-License-Identifier: GFDL-1.1-no-invari      1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
  2                                                     2 
  3 .. _querycap:                                       3 .. _querycap:
  4                                                     4 
  5 *********************                               5 *********************
  6 Querying Capabilities                               6 Querying Capabilities
  7 *********************                               7 *********************
  8                                                     8 
  9 Because V4L2 covers a wide variety of devices       9 Because V4L2 covers a wide variety of devices not all aspects of the API
 10 are equally applicable to all types of devices     10 are equally applicable to all types of devices. Furthermore devices of
 11 the same type have different capabilities and      11 the same type have different capabilities and this specification permits
 12 the omission of a few complicated and less imp     12 the omission of a few complicated and less important parts of the API.
 13                                                    13 
 14 The :ref:`VIDIOC_QUERYCAP` ioctl is available      14 The :ref:`VIDIOC_QUERYCAP` ioctl is available to
 15 check if the kernel device is compatible with      15 check if the kernel device is compatible with this specification, and to
 16 query the :ref:`functions <devices>` and :ref:     16 query the :ref:`functions <devices>` and :ref:`I/O methods <io>`
 17 supported by the device.                           17 supported by the device.
 18                                                    18 
 19 Starting with kernel version 3.1, :ref:`VIDIOC     19 Starting with kernel version 3.1, :ref:`VIDIOC_QUERYCAP`
 20 will return the V4L2 API version used by the d     20 will return the V4L2 API version used by the driver, with generally
 21 matches the Kernel version. There's no need of     21 matches the Kernel version. There's no need of using
 22 :ref:`VIDIOC_QUERYCAP` to check if a specific      22 :ref:`VIDIOC_QUERYCAP` to check if a specific ioctl
 23 is supported, the V4L2 core now returns ``ENOT     23 is supported, the V4L2 core now returns ``ENOTTY`` if a driver doesn't
 24 provide support for an ioctl.                      24 provide support for an ioctl.
 25                                                    25 
 26 Other features can be queried by calling the r     26 Other features can be queried by calling the respective ioctl, for
 27 example :ref:`VIDIOC_ENUMINPUT` to learn about     27 example :ref:`VIDIOC_ENUMINPUT` to learn about the
 28 number, types and names of video connectors on     28 number, types and names of video connectors on the device. Although
 29 abstraction is a major objective of this API,      29 abstraction is a major objective of this API, the
 30 :ref:`VIDIOC_QUERYCAP` ioctl also allows drive     30 :ref:`VIDIOC_QUERYCAP` ioctl also allows driver
 31 specific applications to reliably identify the     31 specific applications to reliably identify the driver.
 32                                                    32 
 33 All V4L2 drivers must support :ref:`VIDIOC_QUE     33 All V4L2 drivers must support :ref:`VIDIOC_QUERYCAP`.
 34 Applications should always call this ioctl aft     34 Applications should always call this ioctl after opening the device.
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php