From: Paul Kocialkowski <contact@paulk.fr>
To: Tomasz Figa <tfiga@chromium.org>
Cc: Alexandre Courbot <acourbot@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Pawel Osciak <posciak@chromium.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2] media: docs-rst: Document m2m stateless video decoder interface
Date: Tue, 09 Oct 2018 19:48:09 +0200 [thread overview]
Message-ID: <21f6b66ea646c6e24e5801023557e8b5db3831d6.camel@paulk.fr> (raw)
In-Reply-To: <CAAFQd5A4t1F9kqepJ+11GJj7zJWKTp-bD1aCNL0N1w9Qeqtmuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
Hi,
Le mardi 09 octobre 2018 à 16:30 +0900, Tomasz Figa a écrit :
> On Thu, Oct 4, 2018 at 9:46 PM Paul Kocialkowski <contact@paulk.fr> wrote:
> >
> > Hi,
> >
> > Here are a few minor suggestion about H.264 controls.
> >
> > Le jeudi 04 octobre 2018 à 17:11 +0900, Alexandre Courbot a écrit :
> > > diff --git a/Documentation/media/uapi/v4l/extended-controls.rst b/Documentation/media/uapi/v4l/extended-controls.rst
> > > index a9252225b63e..9d06d853d4ff 100644
> > > --- a/Documentation/media/uapi/v4l/extended-controls.rst
> > > +++ b/Documentation/media/uapi/v4l/extended-controls.rst
> > > @@ -810,6 +810,31 @@ enum v4l2_mpeg_video_bitrate_mode -
> > > otherwise the decoder expects a single frame in per buffer.
> > > Applicable to the decoder, all codecs.
> > >
> > > +.. _v4l2-mpeg-h264:
> > > +
> > > +``V4L2_CID_MPEG_VIDEO_H264_SPS``
> > > + Instance of struct v4l2_ctrl_h264_sps, containing the SPS of to use with
> > > + the next queued frame. Applicable to the H.264 stateless decoder.
> > > +
> > > +``V4L2_CID_MPEG_VIDEO_H264_PPS``
> > > + Instance of struct v4l2_ctrl_h264_pps, containing the PPS of to use with
> > > + the next queued frame. Applicable to the H.264 stateless decoder.
> > > +
> > > +``V4L2_CID_MPEG_VIDEO_H264_SCALING_MATRIX``
> >
> > For consistency with MPEG-2 and upcoming JPEG, I think we should call
> > this "H264_QUANTIZATION".
>
> I'd rather stay consistent with H.264 specification, which uses the
> wording as defined in Alex's patch. Otherwise it would be difficult to
> correlate between the controls and the specification, which is
> something that the userspace developer would definitely need to
> understand how to properly parse the stream and obtain the decoding
> parameters.
Okay, I agree this makes more sense than trying to keep the names
consistent across codecs.
> >
> > > + Instance of struct v4l2_ctrl_h264_scaling_matrix, containing the scaling
> > > + matrix to use when decoding the next queued frame. Applicable to the H.264
> > > + stateless decoder.
> > > +
> > > +``V4L2_CID_MPEG_VIDEO_H264_SLICE_PARAM``
> >
> > Ditto with "H264_SLICE_PARAMS".
> >
>
> It doesn't seem to be related to the spec in this case and "params"
> sounds better indeed.
Cheers,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-09 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 8:11 [RFC PATCH v2] media: docs-rst: Document m2m stateless video decoder interface Alexandre Courbot
2018-10-04 12:41 ` Paul Kocialkowski
2018-10-09 5:58 ` Tomasz Figa
2018-10-12 12:28 ` Paul Kocialkowski
2018-10-04 12:47 ` Paul Kocialkowski
2018-10-04 18:10 ` Nicolas Dufresne
2018-10-05 17:10 ` Paul Kocialkowski
2018-10-08 10:21 ` Hans Verkuil
2018-10-09 7:36 ` Tomasz Figa
2018-10-12 11:52 ` Paul Kocialkowski
2018-10-09 7:30 ` Tomasz Figa
2018-10-09 17:48 ` Paul Kocialkowski [this message]
2018-10-08 11:01 ` Hans Verkuil
2018-10-09 7:41 ` Tomasz Figa
2018-10-09 8:07 ` Hans Verkuil
2018-10-09 5:48 ` Tomasz Figa
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=21f6b66ea646c6e24e5801023557e8b5db3831d6.camel@paulk.fr \
--to=contact@paulk.fr \
--cc=acourbot@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=posciak@chromium.org \
--cc=tfiga@chromium.org \
/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).