From: Boris Brezillon <boris.brezillon@collabora.com>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh+dt@kernel.org>,
Tomasz Figa <tfiga@chromium.org>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
kernel@collabora.com,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
Sakari Ailus <sakari.ailus@iki.fi>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH v4 5/6] media: rkvdec: Add the rkvdec driver
Date: Fri, 31 Jan 2020 13:18:45 +0100 [thread overview]
Message-ID: <20200131131845.65451a8c@collabora.com> (raw)
In-Reply-To: <739f60a89646cc92f26e34523cbe8aaab5697351.camel@collabora.com>
On Fri, 31 Jan 2020 08:53:47 -0300
Ezequiel Garcia <ezequiel@collabora.com> wrote:
> On Thu, 2020-01-30 at 17:12 +0100, Boris Brezillon wrote:
> > On Wed, 29 Jan 2020 16:55:00 -0300
> > Ezequiel Garcia <ezequiel@collabora.com> wrote:
> >
> > > From: Boris Brezillon <boris.brezillon@collabora.com>
> > >
> > > The rockchip vdec block is a stateless decoder that's able to decode
> > > H264, HEVC and VP9 content. This commit adds the core infrastructure
> > > and the H264 backend. Support for VP9 and HEVS will be added later on.
^HEVC
> > >
> > > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> > > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> > > ---
> > > v4:
> > > * Make poc tables const, as suggested by Hans
> > > * Move buffer extra space calculation TRY_FMT, as done on Hantro.
> > > * Get rid of vb2_request_get_buf and open-code
> > > following Cedrus. We can move it to a helper as a follow-up patch.
> >
> > Well, we know what that means in practice :-).
> >
>
> Well, not necesarily. I think we can expect a helper soon,
> but it doesn't have to be part of this series :-)
I'd be happy to be proven wrong ;-).
next prev parent reply other threads:[~2020-01-31 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 19:54 [PATCH v4 0/6] media: rockchip: Add the rkvdec driver Ezequiel Garcia
2020-01-29 19:54 ` [PATCH v4 1/6] media: uapi: h264: Add DPB entry field reference flags Ezequiel Garcia
2020-01-29 19:54 ` [PATCH v4 2/6] media: v4l2-core: Add helpers to build the H264 P/B0/B1 reflists Ezequiel Garcia
2020-01-29 19:54 ` [PATCH v4 3/6] media: hantro: h264: Use the generic H264 reflist builder Ezequiel Garcia
2020-01-29 19:54 ` [PATCH v4 4/6] media: dt-bindings: rockchip: Document RK3399 Video Decoder bindings Ezequiel Garcia
2020-01-29 19:55 ` [PATCH v4 5/6] media: rkvdec: Add the rkvdec driver Ezequiel Garcia
2020-01-30 16:12 ` Boris Brezillon
2020-01-31 11:53 ` Ezequiel Garcia
2020-01-31 12:18 ` Boris Brezillon [this message]
2020-01-29 19:55 ` [PATCH v4 6/6] arm64: dts: rockchip: rk3399: Define the rockchip Video Decoder node Ezequiel Garcia
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=20200131131845.65451a8c@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas@ndufresne.ca \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--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).