Hi Sakari,
3 small details
On Fri, Nov 22, 2024 at 12:06:29PM +0200, Sakari Ailus wrote:
> Sub-device configuration models define what V4L2 API elements are
> available on a compliant sub-device and how do they behave.
>
> The patch also adds a model for common raw sensors.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx>
[SNIP]
> +
> +The combination of the analogue crop and binning, sub-sampling and scaling
> +operations may result in an image size that may be larger than desirable. For
> +this purpose, a digital crop operation may be performed on the image after these
> +operations. The resulting image size is further output by the sensor.
> +
> +Drivers may only support some of even none of these configurations, in which
|
+-> or ?
> +case they do not expose the corresponding selection rectangles.
> +
> +Also refer to :ref:`Selection targets <v4l2-selection-targets-table>`.
> +
> +.. flat-table:: Selection targets on pads
> + :header-rows: 1
> +
> + * - Pad/Stream
> + - Selection target/format
> + - Mandatory (X/-)
> + - Modifiable (X/-)
> + - Synopsis
> + * - 1/0
> + - Format
> + - X
> + - \-
> + - Image data format. The width and height fields of this format are the
> + same than those for the V4L2_SEL_TGT_CROP_BOUNDS rectangle. The media
--------------
|
+-> same as
> + bus code of this format reflects the native pixel depth of the sensor.
> + * - 1/0
> + - V4L2_SEL_TGT_CROP_BOUNDS
> + - X
> + - \-
> + - X
> + - Digital crop. This rectangle is relative to the V4L2_SEL_TGT_COMPOSE
> + rectangle on (pad, stream) pair 1/0.
> + * - 0/0
> + - Format
> + - X
> + - X
> + - Image data source format. The width and height fields of the format are
> + the same than for the V4L2_SEL_TGT_CROP rectangle on (pad, stream) pair
--------
|
+-> same as
> + 0/0 and the media bus code reflects the pixel data output of the sensor.
> + * - 0/1
> + - Format
> + - X
> + - \-
> + - Embedded data source format.
> +
--
Kind Regards
Mehdi Djait
