From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] doc: media: Document VP9 reference_mode miss-placement
Date: Tue, 22 Feb 2022 09:22:34 +0100 [thread overview]
Message-ID: <ae6ca701-2296-8907-cead-cb2c1f469d4a@collabora.com> (raw)
In-Reply-To: <20220221193728.808414-1-nicolas.dufresne@collabora.com>
Hi Nicolas,
Thanks,
BTW There's a typo in the text, please see below, but other than that
Reviewed-by: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
W dniu 21.02.2022 o 20:37, Nicolas Dufresne pisze:
> The reference_mode derived syntax is part of the compressed headers and
> should have been moved into the corresponding control structure. Document
> this mistake. The value can be set to 0 if the driver does not require
> compressed headers information.
>
> Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> ---
> .../userspace-api/media/v4l/ext-ctrls-codec-stateless.rst | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
> index cc080c4257d01..ec48e4acb5ece 100644
> --- a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
> +++ b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
> @@ -1692,7 +1692,12 @@ See section '7.3.1 Tx mode semantics' of the :ref:`vp9` specification for more d
> * - __u8
> - ``reference_mode``
> - Specifies the type of inter prediction to be used. See
> - :ref:`Reference Mode<vp9_reference_mode>` for more details.
> + :ref:`Reference Mode<vp9_reference_mode>` for more details. Note that
> + this is derived as part of the compressed header parsing process and
> + for this reason should have bee part of
should have been
> + :c:type: `v4l2_ctrl_vp9_compressed_hdr` optional control. It is safe to
> + set this value to zero if the driver does not require compressed
> + headers.
> * - __u8
> - ``reserved[7]``
> - Applications and drivers must set this to zero.
prev parent reply other threads:[~2022-02-22 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 19:37 Nicolas Dufresne
2022-02-22 8:22 ` Andrzej Pietrasiewicz [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=ae6ca701-2296-8907-cead-cb2c1f469d4a@collabora.com \
--to=andrzej.p@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®