On 11/07/18 16:04, Sakari Ailus wrote:
> The NATIVE_SIZE target is documented for mem2mem devices but no driver has
> ever apparently used it. It may be never needed; remove it for now.
>
> Suggested-by: Hans Verkuil <hans.verk...@cisco.com>
> Signed-off-by: Sakari Ailus <sakari.ai...@linux.intel.com>
Acked-by: Hans Verkuil <hans.verk...@cisco.com>
Thanks,
Hans
> ---
> Documentation/media/uapi/v4l/v4l2-selection-targets.rst | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/Documentation/media/uapi/v4l/v4l2-selection-targets.rst
> b/Documentation/media/uapi/v4l/v4l2-selection-targets.rst
> index 87433ec76c6b..bee31611947e 100644
> --- a/Documentation/media/uapi/v4l/v4l2-selection-targets.rst
> +++ b/Documentation/media/uapi/v4l/v4l2-selection-targets.rst
> @@ -42,12 +42,7 @@ of the two interfaces they are used.
> * - ``V4L2_SEL_TGT_NATIVE_SIZE``
> - 0x0003
> - The native size of the device, e.g. a sensor's pixel array.
> - ``left`` and ``top`` fields are zero for this target. Setting the
> - native size will generally only make sense for memory to memory
> - devices where the software can create a canvas of a given size in
> - which for example a video frame can be composed. In that case
> - V4L2_SEL_TGT_NATIVE_SIZE can be used to configure the size of
> - that canvas.
> + ``left`` and ``top`` fields are zero for this target.
> - Yes
> - Yes
> * - ``V4L2_SEL_TGT_COMPOSE``
>
