Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) .. _v4l2-selections-common:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) Common selection definitions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) ============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) While the :ref:`V4L2 selection API <selection-api>` and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) similar, there's one fundamental difference between the two. On
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) sub-device API, the selection rectangle refers to the media bus format,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) and is bound to a sub-device's pad. On the V4L2 interface the selection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) rectangles refer to the in-memory pixel format.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) This section defines the common definitions of the selection interfaces
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) on the two APIs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) .. toctree::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)     :maxdepth: 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)     v4l2-selection-targets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23)     v4l2-selection-flags