From: Boris Brezillon <boris.brezillon@collabora.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Ezequiel Garcia <ezequiel@collabora.com>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH v4 01/10] rockchip/vpu: rename from rockchip to hantro
Date: Wed, 12 Jun 2019 10:23:16 +0200 [thread overview]
Message-ID: <20190612102316.271e8d27@collabora.com> (raw)
In-Reply-To: <VI1PR03MB4206D849E9815A7704D175DBACEC0@VI1PR03MB4206.eurprd03.prod.outlook.com>
On Wed, 12 Jun 2019 08:14:35 +0000
Jonas Karlman <jonas@kwiboo.se> wrote:
> On 2019-06-11 14:50, Philipp Zabel wrote:
> > Rename the driver and all relevant identifiers from Rockchip to Hantro,
> > as other Hantro IP based VPU implementations can be supported by the
> > same driver.
> > The RK3288 decoder is Hantro G1 based, the encoder is Hantro H1.
>
> The RK3288 has two VPU blocks that is described as a VPU combo in the datasheet,
> VPU1 (the G1) and a HEVC decoder (not sharing the Hantro G2 hw regs).
> Similarly the RK3399 has two VPU blocks, VPU2 based on G1 but with regs/fields re-ranged
> and the RKVDPU (new generation of the HEVC block found in RK3288).
>
> How can we expose these secondary blocks once rockchip vpu driver has transitioned
> into a hantro driver? Should a new rockchip vpu driver be created for the HEVC/RKVDEC blocks?
Yes, if those are not Hantro IPs a new driver should be created. I'm
currently working on providing generic m2m helpers for stateless codecs
to limit the code duplication incurred by this split. The good thing is
that it should also help shrink the code of the cedrus driver (and more
generally all stateless codec drivers).
next prev parent reply other threads:[~2019-06-12 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:50 [PATCH v4 00/10] Rename Rockchip VPU driver to Hantro, add initial i.MX8M support Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 01/10] rockchip/vpu: rename from rockchip to hantro Philipp Zabel
2019-06-12 8:14 ` Jonas Karlman
2019-06-12 8:23 ` Boris Brezillon [this message]
2019-06-11 12:50 ` [PATCH v4 02/10] media: hantro: print video device name in addition to device node Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 03/10] media: hantro: add PM runtime resume callback Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 04/10] media: hantro: make irq names configurable Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 05/10] media: hantro: add support for named register ranges Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 06/10] media: hantro: add support for separate control block Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 07/10] media: hantro: allow arbitrary number of clocks Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 08/10] media: dt-bindings: Document i.MX8MQ and i.MX8MM VPU bindings Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 09/10] media: hantro: add initial i.MX8MQ support Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 10/10] media: hantro: add initial i.MX8MM support (untested) Philipp Zabel
2019-06-12 7:55 ` [PATCH v4 00/10] Rename Rockchip VPU driver to Hantro, add initial i.MX8M support Hans Verkuil
2019-06-12 8:00 ` Hans Verkuil
2019-06-12 8:30 ` Boris Brezillon
2019-06-12 9:46 ` Philipp Zabel
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=20190612102316.271e8d27@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
/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.