From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Tomasz Figa <tfiga@chromium.org>
Cc: "list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>,
" <linux-arm-kernel@lists.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Courbot <acourbot@chromium.org>,
Jonas Karlman <jonas@kwiboo.se>,
jenskuske@gmail.com, linux-sunxi@googlegroups.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Guenter Roeck <groeck@chromium.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
Pawel Osciak <posciak@chromium.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] media: uapi: Add H264 low-level decoder API compound controls.
Date: Mon, 18 Mar 2019 16:47:00 +0100 [thread overview]
Message-ID: <20190318154700.4qks2qfxown2frgk@flea> (raw)
In-Reply-To: <CAAFQd5BeiGVvDcZTFVYg_Qbw1NxRcWFybW2FcDGE=ohFWHFbYA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2006 bytes --]
On Thu, Mar 14, 2019 at 01:13:33PM +0900, Tomasz Figa wrote:
> On Thu, Mar 14, 2019 at 12:31 AM Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> >
> > Hi Tomasz,
> >
> > On Fri, Mar 08, 2019 at 03:12:18PM +0900, Tomasz Figa wrote:
> > > > +.. _v4l2-mpeg-h264:
> > > > +
> > > > +``V4L2_CID_MPEG_VIDEO_H264_SPS (struct)``
> > > > + Specifies the sequence parameter set (as extracted from the
> > > > + bitstream) for the associated H264 slice data. This includes the
> > > > + necessary parameters for configuring a stateless hardware decoding
> > > > + pipeline for H264. The bitstream parameters are defined according
> > > > + to :ref:`h264`. Unless there's a specific comment, refer to the
> > > > + specification for the documentation of these fields, section 7.4.2.1.1
> > > > + "Sequence Parameter Set Data Semantics".
> > >
> > > I don't see this section being added by this patch. Where does it come from?
> >
> > This is referring to the the H264 spec itself, as I was trying to
> > point out with the reference in that paragraph. How would you write
> > this down to make it more obvious?
> >
>
> Aha, somehow it didn't come to my mind when reading it. How about
> something like below?
>
> Unless there is a specific comment, refer to the ITU-T Rec. H.264
> specification, section "7.4.2.1.1 Sequence parameter set data semantics"
> (as of the 04/2017 edition).
The :ref:`h264` currently expands to "ITU H.264", which means in the
documentation, in the case above, it ends up as
The bitstream parameters are defined according to ITU H.264. Unless
there’s a specific comment, refer to the specification for the
documentation of these fields, section 7.4.2.1.1 “Sequence Parameter
Set Data Semantics”.
I could change the reference to have "ITU-T Rec. H.264 Specification
(04/2017 Edition)". Would that work for you?
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-18 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 13:19 [PATCH v5 0/2] media: cedrus: Add H264 decoding support Maxime Ripard
2019-03-07 13:19 ` [PATCH v5 1/2] media: uapi: Add H264 low-level decoder API compound controls Maxime Ripard
2019-03-08 6:12 ` Tomasz Figa
2019-03-13 15:31 ` Maxime Ripard
2019-03-14 4:13 ` Tomasz Figa
2019-03-18 15:47 ` Maxime Ripard [this message]
2019-03-19 4:03 ` Tomasz Figa
2019-03-07 13:19 ` [PATCH v5 2/2] media: cedrus: Add H264 decoding support Maxime Ripard
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=20190318154700.4qks2qfxown2frgk@flea \
--to=maxime.ripard@bootlin.com \
--cc=acourbot@chromium.org \
--cc=ezequiel@collabora.com \
--cc=groeck@chromium.org \
--cc=hans.verkuil@cisco.com \
--cc=jenskuske@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=nicolas.dufresne@collabora.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=posciak@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wens@csie.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