[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1526297247-20881-5-git-send-email-luca@lucaceresoli.net>
Date: Mon, 14 May 2018 13:27:27 +0200
From: Luca Ceresoli <luca@...aceresoli.net>
To: linux-media@...r.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-kernel@...r.kernel.org,
Luca Ceresoli <luca@...aceresoli.net>,
Hans Verkuil <hverkuil@...all.nl>
Subject: [PATCH v2 5/5] media: docs: selection: fix misleading sentence about the CROP API
The API limitation described here is about the CROP API, not about the
entire V4L2.
Cc: Hans Verkuil <hverkuil@...all.nl>
Signed-off-by: Luca Ceresoli <luca@...aceresoli.net>
---
Changed v1 -> v2: nothing.
---
Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst b/Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst
index ba1064a244a0..e7455fb1e572 100644
--- a/Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst
+++ b/Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst
@@ -15,7 +15,7 @@ because the described operation is actually the composing. The
selection API makes a clear distinction between composing and cropping
operations by setting the appropriate targets.
-The V4L2 API lacks any support for composing to and cropping from an
+The CROP API lacks any support for composing to and cropping from an
image inside a memory buffer. The application could configure a
capture device to fill only a part of an image by abusing V4L2
API. Cropping a smaller image from a larger one is achieved by setting
--
2.7.4
Powered by blists - more mailing lists