From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Nicolas Dufresne <nicolas@ndufresne.ca>,
Tomasz Figa <tfiga@chromium.org>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCHv3 1/5] media: docs-rst: Document memory-to-memory video encoder interface
Date: Tue, 23 Jun 2020 12:47:41 +0200 [thread overview]
Message-ID: <20200623124741.2de499cc@coco.lan> (raw)
In-Reply-To: <20200526100932.2626420-2-hverkuil-cisco@xs4all.nl>
Em Tue, 26 May 2020 12:09:28 +0200
Hans Verkuil <hverkuil-cisco@xs4all.nl> escreveu:
There are some things here that it should be fine for now, but I would like
to be added on our TODO:
> +Conventions and Notations Used in This Document
> +===============================================
...
> +
> +2. The meaning of words "must", "may", "should", etc. is as per `RFC
> + 2119 <https://tools.ietf.org/html/rfc2119>`_.
> +
> +3. All steps not marked "optional" are required.
Those should be moved in the future to the media uAPI spec as a hole.
> +
> +4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
> + interchangeably with :c:func:`VIDIOC_G_CTRL` and :c:func:`VIDIOC_S_CTRL`,
> + unless specified otherwise.
> +
> +5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
> + used interchangeably with multi-planar API, unless specified otherwise,
> + depending on encoder capabilities and following the general V4L2 guidelines.
Probably those too.
> +Glossary
> +========
> +
> +Refer to :ref:`decoder-glossary`.
I have some patches (yet to be merged) for a media glossary. We should move
the decoder one to be at the same place.
Thanks,
Mauro
next prev parent reply other threads:[~2020-06-23 10:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 10:09 [PATCHv3 0/5] Stateful Encoding: final bits Hans Verkuil
2020-05-26 10:09 ` [PATCHv3 1/5] media: docs-rst: Document memory-to-memory video encoder interface Hans Verkuil
2020-05-29 9:57 ` Stanimir Varbanov
2020-05-29 10:17 ` Stanimir Varbanov
2020-05-29 12:21 ` Tomasz Figa
2020-06-05 7:19 ` Stanimir Varbanov
2020-06-05 21:24 ` Nicolas Dufresne
2020-06-06 7:58 ` Stanimir Varbanov
2020-06-07 0:27 ` Nicolas Dufresne
2020-06-10 12:28 ` Tomasz Figa
2020-06-10 13:08 ` Nicolas Dufresne
2020-06-10 13:55 ` Tomasz Figa
2020-06-10 13:58 ` Tomasz Figa
2020-06-23 10:36 ` Hans Verkuil
2020-06-23 11:47 ` Tomasz Figa
2020-06-23 10:47 ` Mauro Carvalho Chehab [this message]
2020-05-26 10:09 ` [PATCHv3 2/5] vidioc-g-parm.rst: update the VIDIOC_G/S_PARM documentation Hans Verkuil
2020-05-28 7:54 ` Michael Tretter
2020-05-26 10:09 ` [PATCHv3 3/5] dev-decoder.rst: small fixes Hans Verkuil
2020-05-26 10:09 ` [PATCHv3 4/5] videodev2.h: add V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL flag Hans Verkuil
2020-05-26 10:09 ` [PATCHv3 5/5] dev-encoder.rst: add reference to V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL Hans Verkuil
2020-05-28 7:58 ` [PATCHv3 0/5] Stateful Encoding: final bits Michael Tretter
2020-06-02 9:01 ` 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=20200623124741.2de499cc@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=nicolas@ndufresne.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.