From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Nicolas Dufresne" <nicolas.dufresne@collabora.com>
Cc: "Sascha Hauer" <s.hauer@pengutronix.de>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Andrzej Pietrasiewicz" <andrzej.p@collabora.com>,
"Hans Verkuil" <hverkuil@kernel.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lucas Sinn" <lucas.sinn@wolfvision.net>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 5/7] media: verisilicon: Add Rockchip VPU720 JPEG decoder
Date: Fri, 21 Aug 2026 06:28:30 +0000 [thread overview]
Message-ID: <6947a89b-8fa0-499a-9be8-c48d9bb5e7a7@pengutronix.de> (raw)
In-Reply-To: <61537689daa428a577e6bdab794d044f5405128e.camel@collabora.com>
On 2026-08-20 12:02, Nicolas Dufresne wrote:
> Hi Sascha,
>
> Le jeudi 20 août 2026 à 10:03 +0000, Sascha Hauer a écrit :
> > On 2026-08-19 11:48, Nicolas Dufresne wrote:
> > > Hi Sascha,
> > >
> > > Le mercredi 19 août 2026 à 12:37 +0200, Sascha Hauer a écrit :
> > > > +/* ------------------------------------------------------------------ */
> > > > +/* Register byte offsets from dec_base */
> > > > +/* ------------------------------------------------------------------ */
> > > > +
> > > > +/* REG0: IP version / product ID */
> > > > +#define VDPU720_REG_VERSION 0x000
> > > > +#define VDPU720_PROD_NUM GENMASK(31, 16)
> > > > +#define VDPU720_BIT_DEPTH BIT(8)
> > >
> > > Can you share a dump and share these register reset values. Looking at the
> > > layout, clearly its highly modified, but probably derived from VSI multi-codec,
> > > but I'm thinking perhaps we'll learn more from that. Its always nice to justify
> > > when adding more chips that are not strictly VSI designs (or maybe it is) to the
> > > hantro dirver.
> >
> > Here's a full register dump right after reset:
> >
> > 00000000: db1f0005 00000004 00120000 00000000
>
> I've look around as much as I could, and could not find any indication that this
> is an IP from VSI or derived from a VSI core. It is entirely different from
> vdpu1 in mpp (proper G1, rk3288 and similar) and vdpu2 (modified G1 / VDPU121).
> In short, this is not a multi-codec core.
>
> So that ball is on your end to show that this driver belongs to hantro rather
> then its own driver. In absence of evidence, this driver should be part of
> rockchip vendor folder, not vsi. Don't read me wrong, I trust that you have
> tested what the LLM have chosen, but anything can be implement in Hantro really,
> it does not mean it should be there.
I won't argue that the driver belongs to hantro because apparently it doesn't.
I don't know where the decision to integrate it into hantro is coming
from, maybe just because the Rockchip JPEG encoder is also there.
Anyway, I'll start with a fresh series with a standalone driver.
Patches 1-3 could be useful on their own though, so you might want to
take them. They are untested on real Hantro hardware, but I could give
them a go on the JPEG encoder.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-08-21 6:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:37 [PATCH 0/7] media: verisilicon: Add RK3588 VPU720 JPEG decoder Sascha Hauer
2026-08-19 10:37 ` [PATCH 1/7] media: verisilicon: Fix the cleanup when a codec ->run() fails Sascha Hauer
2026-08-19 11:23 ` sashiko-bot
2026-08-19 15:05 ` Nicolas Dufresne
2026-08-19 10:37 ` [PATCH 2/7] media: verisilicon: Complete the request on the ->run() error paths Sascha Hauer
2026-08-19 12:19 ` sashiko-bot
2026-08-19 10:37 ` [PATCH 3/7] media: verisilicon: Allow the EOS event to be subscribed Sascha Hauer
2026-08-19 10:37 ` [PATCH 4/7] media: dt-bindings: Add Rockchip RK3588 VPU720 JPEG decoder Sascha Hauer
2026-08-19 10:37 ` [PATCH 5/7] media: verisilicon: Add Rockchip " Sascha Hauer
2026-08-19 11:24 ` sashiko-bot
2026-08-19 12:46 ` Heiko Stübner
2026-08-19 14:12 ` Sascha Hauer
2026-08-19 15:48 ` Nicolas Dufresne
2026-08-20 10:03 ` Sascha Hauer
2026-08-20 16:02 ` Nicolas Dufresne
2026-08-21 6:28 ` Sascha Hauer [this message]
2026-08-21 13:05 ` Nicolas Dufresne
2026-08-19 10:37 ` [PATCH 6/7] media: verisilicon: Enforce a minimum sizeimage for the " Sascha Hauer
2026-08-19 10:37 ` [PATCH 7/7] arm64: dts: rockchip: rk3588: Add VPU720 JPEG decoder node Sascha Hauer
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=6947a89b-8fa0-499a-9be8-c48d9bb5e7a7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andrzej.p@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lucas.sinn@wolfvision.net \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=wenst@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