linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Michael Tretter <m.tretter@pengutronix.de>,
	Tomasz Figa <tfiga@chromium.org>,
	Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: [GIT PULL FOR v5.9] Finalize stateful encoder support
Date: Tue, 2 Jun 2020 12:02:54 +0200	[thread overview]
Message-ID: <741fd4cb-1c56-9546-36da-1993474caf49@xs4all.nl> (raw)

Hi Mauro,

This PR finalizes the stateful encoder support by adding the stateful encoder
spec. It was delayed quite a bit and the main reason was how framerates should
be handled given the constraints of what existing stateful encoder drivers
implemented.

Michael, can you make a allegro patch that sets the V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL
flag in that driver and have it behave according to this updated spec?

Many thanks to all who contributed, with honorable mention of Tomasz who wrote
the original version of this spec.

Regards,

	Hans

The following changes since commit 938b29db3aa9c293c7c1366b16e55e308f1a1ddd:

  media: Documentation: media: Refer to mbus format documentation from CSI-2 docs (2020-05-25 15:47:02 +0200)

are available in the Git repository at:

  git://linuxtv.org/hverkuil/media_tree.git tags/br-stateful-enc

for you to fetch changes up to f73d82aca17259d7409c3bb675c1def0d71041e0:

  dev-encoder.rst: add reference to V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL (2020-06-02 11:05:51 +0200)

----------------------------------------------------------------
Tag branch

----------------------------------------------------------------
Hans Verkuil (4):
      vidioc-g-parm.rst: update the VIDIOC_G/S_PARM documentation
      dev-decoder.rst: small fixes
      videodev2.h: add V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL flag
      dev-encoder.rst: add reference to V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL

Tomasz Figa (1):
      media: docs-rst: Document memory-to-memory video encoder interface

 Documentation/userspace-api/media/v4l/dev-decoder.rst        |   6 +-
 Documentation/userspace-api/media/v4l/dev-encoder.rst        | 729 ++++++++++++++++++++++++++++++++++++++++
 Documentation/userspace-api/media/v4l/dev-mem2mem.rst        |   1 +
 Documentation/userspace-api/media/v4l/pixfmt-v4l2.rst        |   5 +
 Documentation/userspace-api/media/v4l/v4l2.rst               |   2 +
 Documentation/userspace-api/media/v4l/vidioc-encoder-cmd.rst |  51 +--
 Documentation/userspace-api/media/v4l/vidioc-enum-fmt.rst    |  30 +-
 Documentation/userspace-api/media/v4l/vidioc-g-parm.rst      |  51 +--
 Documentation/userspace-api/media/videodev2.h.rst.exceptions |   1 +
 include/uapi/linux/videodev2.h                               |   1 +
 10 files changed, 830 insertions(+), 47 deletions(-)
 create mode 100644 Documentation/userspace-api/media/v4l/dev-encoder.rst

             reply	other threads:[~2020-06-02 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 10:02 Hans Verkuil [this message]
2020-06-02 10:34 ` [GIT PULL FOR v5.9] Finalize stateful encoder support (#64176) Jenkins
2020-06-23 10:39 ` [GIT PULL FOR v5.9] Finalize stateful encoder support Mauro Carvalho Chehab

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=741fd4cb-1c56-9546-36da-1993474caf49@xs4all.nl \
    --to=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 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).