linux/Documentation/linux_tv/media/v4l/vidioc-cropcap.rst

.. -*- coding: utf-8; mode: rst -*-

.. _VIDIOC_CROPCAP:

********************
ioctl VIDIOC_CROPCAP
********************

*man VIDIOC_CROPCAP(2)*

Information about the video cropping and scaling abilities


Synopsis
========

.. cpp:function:: int ioctl( int fd, int request, struct v4l2_cropcap *argp )

Arguments
=========

``fd``
    File descriptor returned by :ref:`open() <func-open>`.

``request``
    VIDIOC_CROPCAP

``argp``


Description
===========

Applications use this function to query the cropping limits, the pixel
aspect of images and to calculate scale factors. They set the ``type``
field of a v4l2_cropcap structure to the respective buffer (stream)
type and call the :ref:`VIDIOC_CROPCAP` ioctl with a pointer to this
structure. Drivers fill the rest of the structure. The results are
constant except when switching the video standard. Remember this switch
can occur implicit when switching the video input or output.

Do not use the multiplanar buffer types. Use
``V4L2_BUF_TYPE_VIDEO_CAPTURE`` instead of
``V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE`` and use
``V4L2_BUF_TYPE_VIDEO_OUTPUT`` instead of
``V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE``.

This ioctl must be implemented for video capture or output devices that
support cropping and/or scaling and/or have non-square pixels, and for
overlay devices.


.. _v4l2-cropcap:

.. flat-table:: struct v4l2_cropcap
    :header-rows:  0
    :stub-columns: 0
    :widths:       1 1 2


    -  .. row 1

       -  __u32

       -  ``type``

       -  Type of the data stream, set by the application. Only these types
          are valid here: ``V4L2_BUF_TYPE_VIDEO_CAPTURE``,
          ``V4L2_BUF_TYPE_VIDEO_OUTPUT`` and
          ``V4L2_BUF_TYPE_VIDEO_OVERLAY``. See :ref:`v4l2-buf-type`.

    -  .. row 2

       -  struct :ref:`v4l2_rect <v4l2-rect-crop>`

       -  ``bounds``

       -  Defines the window within capturing or output is possible, this
          may exclude for example the horizontal and vertical blanking
          areas. The cropping rectangle cannot exceed these limits. Width
          and height are defined in pixels, the driver writer is free to
          choose origin and units of the coordinate system in the analog
          domain.

    -  .. row 3

       -  struct :ref:`v4l2_rect <v4l2-rect-crop>`

       -  ``defrect``

       -  Default cropping rectangle, it shall cover the "whole picture".
          Assuming pixel aspect 1/1 this could be for example a 640 × 480
          rectangle for NTSC, a 768 × 576 rectangle for PAL and SECAM
          centered over the active picture area. The same co-ordinate system
          as for ``bounds`` is used.

    -  .. row 4

       -  struct :ref:`v4l2_fract <v4l2-fract>`

       -  ``pixelaspect``

       -  This is the pixel aspect (y / x) when no scaling is applied, the
          ratio of the actual sampling frequency and the frequency required
          to get square pixels.

          When cropping coordinates refer to square pixels, the driver sets
          ``pixelaspect`` to 1/1. Other common values are 54/59 for PAL and
          SECAM, 11/10 for NTSC sampled according to [:ref:`itu601`].



.. _v4l2-rect-crop:

.. flat-table:: struct v4l2_rect
    :header-rows:  0
    :stub-columns: 0
    :widths:       1 1 2


    -  .. row 1

       -  __s32

       -  ``left``

       -  Horizontal offset of the top, left corner of the rectangle, in
          pixels.

    -  .. row 2

       -  __s32

       -  ``top``

       -  Vertical offset of the top, left corner of the rectangle, in
          pixels.

    -  .. row 3

       -  __u32

       -  ``width``

       -  Width of the rectangle, in pixels.

    -  .. row 4

       -  __u32

       -  ``height``

       -  Height of the rectangle, in pixels.



Return Value
============

On success 0 is returned, on error -1 and the ``errno`` variable is set
appropriately. The generic error codes are described at the
:ref:`Generic Error Codes <gen-errors>` chapter.

EINVAL
    The struct :ref:`v4l2_cropcap <v4l2-cropcap>` ``type`` is
    invalid.


.. ------------------------------------------------------------------------------
.. This file was automatically converted from DocBook-XML with the dbxml
.. library (https://github.com/return42/sphkerneldoc). The origin XML comes
.. from the linux kernel, refer to:
..
.. * https://github.com/torvalds/linux/tree/master/Documentation/DocBook
.. ------------------------------------------------------------------------------