From: Tomasz Figa <tfiga@chromium.org>
To: linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Paweł Ościak" <posciak@chromium.org>,
"Alexandre Courbot" <acourbot@chromium.org>,
"Kamil Debski" <kamil@wypas.org>,
"Andrzej Hajda" <a.hajda@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Jeongtae Park" <jtp.park@samsung.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Tiffany Lin" <tiffany.lin@mediatek.com>,
"Andrew-CT Chen" <andrew-ct.chen@mediatek.com>,
"Stanimir Varbanov" <stanimir.varbanov@linaro.org>,
"Todor Tomov" <todor.tomov@linaro.org>,
"Nicolas Dufresne" <nicolas@ndufresne.ca>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Tomasz Figa" <tfiga@chromium.org>
Subject: [RFC PATCH 0/2] Document the V4L2 (stateful) Codec API
Date: Tue, 5 Jun 2018 19:33:26 +0900 [thread overview]
Message-ID: <20180605103328.176255-1-tfiga@chromium.org> (raw)
This series attempts to add the documentation of what was discussed
during Media Workshops at LinuxCon Europe 2012 in Barcelona and then
later Embedded Linux Conference Europe 2014 in Düsseldorf and then
eventually written down by Pawel Osciak and tweaked a bit by Chrome OS
video team (but mostly in a cosmetic way or making the document more
precise), during the several years of Chrome OS using the APIs in
production.
Note that most, if not all, of the API is already implemented in
existing mainline drivers, such as s5p-mfc or mtk-vcodec. Intention of
this series is just to formalize what we already have.
It is an initial conversion from Google Docs to RST, so formatting is
likely to need some further polishing. It is also the first time for me
to create such long RST documention. I could not find any other instance
of similar userspace sequence specifications among our Media documents,
so I mostly followed what was there in the source. Feel free to suggest
a better format.
Much of credits should go to Pawel Osciak, for writing most of the
original text.
Tomasz Figa (2):
media: docs-rst: Add decoder UAPI specification to Codec Interfaces
media: docs-rst: Add encoder UAPI specification to Codec Interfaces
Documentation/media/uapi/v4l/dev-codec.rst | 1084 ++++++++++++++++++++
Documentation/media/uapi/v4l/v4l2.rst | 14 +-
2 files changed, 1097 insertions(+), 1 deletion(-)
--
2.17.1.1185.g55be947832-goog
next reply other threads:[~2018-06-05 10:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 10:33 Tomasz Figa [this message]
2018-06-05 10:33 ` [RFC PATCH 1/2] media: docs-rst: Add decoder UAPI specification to Codec Interfaces Tomasz Figa
2018-06-05 11:41 ` Philipp Zabel
2018-06-05 13:42 ` Tomasz Figa
2018-06-06 10:44 ` Philipp Zabel
2018-06-07 7:27 ` Tomasz Figa
2018-06-07 17:49 ` Nicolas Dufresne
2018-06-06 13:02 ` Alexandre Courbot
2018-06-05 13:10 ` Dave Stevenson
2018-06-06 9:03 ` Tomasz Figa
2018-06-06 13:13 ` Alexandre Courbot
2018-06-07 7:21 ` Hans Verkuil
2018-06-07 7:30 ` Tomasz Figa
2018-06-07 17:53 ` Nicolas Dufresne
2018-06-07 19:36 ` Hans Verkuil
2018-06-07 8:47 ` Hans Verkuil
2018-06-07 11:01 ` Philipp Zabel
2018-06-08 9:03 ` Tomasz Figa
2018-06-08 10:13 ` Hans Verkuil
2018-06-07 17:30 ` Nicolas Dufresne
2018-06-08 10:42 ` Tomasz Figa
2018-06-14 12:34 ` Stanimir Varbanov
2018-06-14 13:56 ` Nicolas Dufresne
2018-06-15 8:02 ` Tomasz Figa
2018-09-11 2:26 ` Nicolas Dufresne
2018-09-11 3:10 ` Tomasz Figa
2018-06-05 10:33 ` [RFC PATCH 2/2] media: docs-rst: Add encoder " Tomasz Figa
2018-06-05 11:53 ` Philipp Zabel
2018-06-05 12:31 ` Tomasz Figa
2018-06-05 14:22 ` Philipp Zabel
2018-06-06 9:17 ` Tomasz Figa
2018-06-06 9:40 ` Philipp Zabel
2018-06-06 10:37 ` Tomasz Figa
2018-06-07 7:27 ` Hans Verkuil
2018-06-07 10:32 ` Philipp Zabel
2018-06-07 10:54 ` Hans Verkuil
2018-06-07 11:02 ` Philipp Zabel
2018-06-07 9:21 ` Hans Verkuil
2018-06-07 10:39 ` Philipp Zabel
2018-06-11 7:49 ` 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=20180605103328.176255-1-tfiga@chromium.org \
--to=tfiga@chromium.org \
--cc=a.hajda@samsung.com \
--cc=acourbot@chromium.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=hverkuil@xs4all.nl \
--cc=jtp.park@samsung.com \
--cc=kamil@wypas.org \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=paul.kocialkowski@bootlin.com \
--cc=posciak@chromium.org \
--cc=stanimir.varbanov@linaro.org \
--cc=tiffany.lin@mediatek.com \
--cc=todor.tomov@linaro.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
all inboxes | Powered by JetHome®