From: Alexandre Courbot <acourbot@chromium.org>
To: Helen Koike <helen@koikeco.de>
Cc: "Jian-Jia Su" <jjsu@chromium.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Helen Koike" <helen.koike@collabora.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: v4l2-dev/ioctl: Fix document for VIDIOC_QUERYCAP
Date: Mon, 27 Jul 2020 18:18:41 +0900 [thread overview]
Message-ID: <CAPBb6MW4qD8+1vW4HYb5Fg0Q-kMsHcQebRE-_4a4CSHpNcEFMw@mail.gmail.com> (raw)
In-Reply-To: <91e92ed1-5364-884d-79ab-20d64594deb2@koikeco.de>
On Tue, Jul 21, 2020 at 4:45 AM Helen Koike <helen@koikeco.de> wrote:
>
> Hi,
>
> On 7/20/20 6:29 AM, Jian-Jia Su wrote:
> > V4L2_CAP_VIDEO_M2M is documented as 0x00004000
> > V4L2_CAP_VIDEO_M2M_MPLANE is documented as 0x00008000
> > This is different from the definition in include/uapi/linux/videodev2.h
> >
>
> Nice catch, they are swapped in the docs indeed.
>
> From videodev2.h:
>
> /* Is a video mem-to-mem device that supports multiplanar formats */
> #define V4L2_CAP_VIDEO_M2M_MPLANE 0x00004000
> /* Is a video mem-to-mem device */
> #define V4L2_CAP_VIDEO_M2M 0x00008000
>
> > Signed-off-by: Jian-Jia Su <jjsu@chromium.org>
>
> Reviewed-by: Helen Koike <helen.koike@collabora.com>
FWIW,
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
>
> Regards,
> Helen
>
> > ---
> > Documentation/userspace-api/media/v4l/vidioc-querycap.rst | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/userspace-api/media/v4l/vidioc-querycap.rst b/Documentation/userspace-api/media/v4l/vidioc-querycap.rst
> > index 666ac4d420519..90347367ef06a 100644
> > --- a/Documentation/userspace-api/media/v4l/vidioc-querycap.rst
> > +++ b/Documentation/userspace-api/media/v4l/vidioc-querycap.rst
> > @@ -168,11 +168,11 @@ specification the ioctl returns an ``EINVAL`` error code.
> > - The device supports the :ref:`multi-planar API <planar-apis>`
> > through the :ref:`Video Output <output>` interface.
> > * - ``V4L2_CAP_VIDEO_M2M``
> > - - 0x00004000
> > + - 0x00008000
> > - The device supports the single-planar API through the Video
> > Memory-To-Memory interface.
> > * - ``V4L2_CAP_VIDEO_M2M_MPLANE``
> > - - 0x00008000
> > + - 0x00004000
> > - The device supports the :ref:`multi-planar API <planar-apis>`
> > through the Video Memory-To-Memory interface.
> > * - ``V4L2_CAP_VIDEO_OVERLAY``
> >
prev parent reply other threads:[~2020-07-27 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 9:29 [PATCH] media: v4l2-dev/ioctl: Fix document for VIDIOC_QUERYCAP Jian-Jia Su
2020-07-20 19:45 ` Helen Koike
2020-07-27 9:18 ` Alexandre Courbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPBb6MW4qD8+1vW4HYb5Fg0Q-kMsHcQebRE-_4a4CSHpNcEFMw@mail.gmail.com \
--to=acourbot@chromium.org \
--cc=helen.koike@collabora.com \
--cc=helen@koikeco.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jjsu@chromium.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).