diff options
author | Luca Ceresoli | 2018-05-14 07:27:27 -0400 |
---|---|---|
committer | Mauro Carvalho Chehab | 2018-05-25 15:28:22 -0400 |
commit | e86d1929adae5d5a20617aade8ab19e53297dc4e (patch) | |
tree | 60e527c53e98b3a1a5b650817327ae21dfa20ccc | |
parent | 119e30d3956046b6ae811c00a975ed3c0bf20b9c (diff) |
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.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
-rw-r--r-- | Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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 |