From: Jernej Skrabec <jernej.skrabec@gmail.com>
To: mripard@kernel.org, paul.kocialkowski@bootlin.com
Cc: mchehab@kernel.org, gregkh@linuxfoundation.org, wens@csie.org,
hverkuil-cisco@xs4all.nl, ezequiel@collabora.com,
benjamin.gaignard@collabora.com, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: [PATCH 0/2] media: cedrus: hevc: add support for multiple slices
Date: Sun, 6 Jun 2021 10:23:12 +0200 [thread overview]
Message-ID: <20210606082314.454193-1-jernej.skrabec@gmail.com> (raw)
HEVC frames can be encoded in multiple slices. This short series add
supports for them. First patch adds slice_segment_address to HEVC slice
parameters and second patch implements HEVC multi slice support in
Cedrus.
Question 1: HEVC specs talk about slice_segment_address, but "slice_"
prefix seems redundant in our case, because this field is part of slice
params structure. Should I drop it or leave it?
Question 2: I made slice_segment_address __u32 but __u16 might be
already enough. Which one should it be?
Note: These patches depends on following pull request:
https://www.spinics.net/lists/linux-media/msg193744.html
Jernej Skrabec (2):
media: hevc: Add segment address field
media: cedrus: hevc: Add support for multiple slices
.../media/v4l/ext-ctrls-codec.rst | 3 +++
.../staging/media/sunxi/cedrus/cedrus_h265.c | 26 ++++++++++++-------
.../staging/media/sunxi/cedrus/cedrus_video.c | 1 +
include/media/hevc-ctrls.h | 3 ++-
4 files changed, 22 insertions(+), 11 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-06 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 8:23 Jernej Skrabec [this message]
2021-06-06 8:23 ` [PATCH 1/2] media: hevc: Add segment address field Jernej Skrabec
2021-06-07 7:43 ` Benjamin Gaignard
2021-06-06 8:23 ` [PATCH 2/2] media: cedrus: hevc: Add support for multiple slices Jernej Skrabec
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=20210606082314.454193-1-jernej.skrabec@gmail.com \
--to=jernej.skrabec@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=ezequiel@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@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;
as well as URLs for NNTP newsgroup(s).