From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [PATCH] Documentation: media: improve V4L2_CID_MIN_BUFFERS_FOR_*, doc
Date: Thu, 31 Oct 2024 12:42:19 +0200 [thread overview]
Message-ID: <20241031104219.GF2473@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2a61ded3-4cea-4a1a-9d16-aa74dbb22f74@xs4all.nl>
On Thu, Oct 31, 2024 at 11:26:47AM +0100, Hans Verkuil wrote:
> On 10/31/24 11:11, Laurent Pinchart wrote:
> > Hi Hans,
> >
> > Thank you for the patch.
> >
> > On Thu, Oct 31, 2024 at 08:50:04AM +0100, Hans Verkuil wrote:
> >> Clearly state that the V4L2_CID_MIN_BUFFERS_FOR_OUTPUT and
> >> V4L2_CID_MIN_BUFFERS_FOR_CAPTURE controls are required for
> >> stateful codecs.
> >
> > Wouldn't it be better for this kind of information to be centralized in
> > a stateful decoder document ? That would make it easier for developers
> > to see all they need to implement. Otherwise they would need to read
> > through the whole documentation to pick the parts of the API they need
> > to support in their drivers.
>
> It's also already mentioned in the documentation for the stateful de/encoders here:
>
> https://linuxtv.org/downloads/v4l-dvb-apis-new/userspace-api/v4l/dev-mem2mem.html
OK, then it's fine to have it here too I think.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> Also, once this vicodec patch is merged:
>
> https://patchwork.linuxtv.org/project/linux-media/patch/1dd09050-40ca-4c5b-b985-819731140388@xs4all.nl/
>
> I plan to push v4l2-compliance patches that explicitly test for the presence of
> these controls and fail if they are missing (like they are now in vicodec).
>
> >> Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
> >> ---
> >> Documentation/userspace-api/media/v4l/control.rst | 6 ++++--
> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/Documentation/userspace-api/media/v4l/control.rst b/Documentation/userspace-api/media/v4l/control.rst
> >> index 57893814a1e5..9253cc946f02 100644
> >> --- a/Documentation/userspace-api/media/v4l/control.rst
> >> +++ b/Documentation/userspace-api/media/v4l/control.rst
> >> @@ -290,13 +290,15 @@ Control IDs
> >> This is a read-only control that can be read by the application and
> >> used as a hint to determine the number of CAPTURE buffers to pass to
> >> REQBUFS. The value is the minimum number of CAPTURE buffers that is
> >> - necessary for hardware to work.
> >> + necessary for hardware to work. This control is required for stateful
> >> + decoders.
> >>
> >> ``V4L2_CID_MIN_BUFFERS_FOR_OUTPUT`` ``(integer)``
> >> This is a read-only control that can be read by the application and
> >> used as a hint to determine the number of OUTPUT buffers to pass to
> >> REQBUFS. The value is the minimum number of OUTPUT buffers that is
> >> - necessary for hardware to work.
> >> + necessary for hardware to work. This control is required for stateful
> >> + encoders.
> >>
> >> .. _v4l2-alpha-component:
> >>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-10-31 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 7:50 [PATCH] Documentation: media: improve V4L2_CID_MIN_BUFFERS_FOR_*, doc Hans Verkuil
2024-10-31 10:11 ` Laurent Pinchart
2024-10-31 10:26 ` Hans Verkuil
2024-10-31 10:42 ` Laurent Pinchart [this message]
2024-10-31 13:37 ` Nicolas Dufresne
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=20241031104219.GF2473@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
/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