From: Dang Huynh <dang.huynh@mainlining.org>
To: "Detlev Casanova" <detlev.casanova@collabora.com>,
"Olivier Crête" <olivier.crete@collabora.com>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Diederik de Haas" <diederik@cknow-tech.com>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Dragan Simic" <dsimic@manjaro.org>,
"Chukun Pan" <amadeus@jmu.edu.cn>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Christian Hewitt" <christianshewitt@gmail.com>
Subject: Re: [PATCH v2 0/3] media: rockchip: rkvdec: add support for the VDPU346 variant
Date: Sat, 03 Jan 2026 20:10:08 +0000 [thread overview]
Message-ID: <8993014.lOV4Wx5bFT@melttower> (raw)
In-Reply-To: <20251226113140.573759-1-christianshewitt@gmail.com>
Hi Christian,
On Friday, December 26, 2025 11:31:37 AM Coordinated Universal Time Christian
Hewitt wrote:
> This series depends upon Detlev Casanova's current v7 series for VDPU381 and
> VDPU383 support [0]. It adds support for the VDPU346 IP block used for
> H264, HEVC and (in active work) VP9 on the RK356X boards. VDPU346 appears
> to be a close relation to VDPU381 used with RK3588, except with a single
> core, output limited to 4K, and minor feature differences, e.g. HEVC level
> 5.1 on VDPU346 vs 6.1 on VDPU381. To handle differences we declare a new
> compatible.
>
> The device-tree changes are derived from prior-art in Detlev's patches for
> RK3576 and RK3588, the vendor kernel [1], and some earlier patch attempts
> from Piotr Oniszczuk and Diederik de Haas.
>
> The register differences between VDPU346 and VDPU381 appear to be minimal so
> we currently and intentionally reuse the VDPU381 h264, hevc, and regs files
> to avoid duplicating code. There is some evidence of buffer size changes in
> testing which still need to be explored. If further register analysis needs
> separate files for VDPU346 the refactoring will be beyond my current n00b
> coding skills and I will either need some coaching or would be happy to
> pass the series over to a more experienced developer.
>
> NB: Testing with the v1 series showed lower mbps bitrate performance. This
> appears to be resolved though it's unclear to me whether this results from
> kernel changes or the ongoing reworking of ffmpeg v4l2_request support [2].
> However with my current Linux 6.19-rc2 test branch [3] I'm now able to play
> Jellyfish H264 and HEVC test media over 100mbps.
>
> Changes since v1:
> - Drop DO-NOT-MERGE patch as changes included in Detvlev v7 series
> - Adapt to variant/capability changes in Detlev's v7 series
> - Add bindings ack from Rob
> - Add rkvdec ack from Nicolas
> - Rebase against Linux 6.19-rc2
>
> [0] https://patchwork.kernel.org/project/linux-rockchip/list/?series=1034794
> [1]
> https://github.com/rockchip-linux/kernel/blob/develop-6.6/arch/arm64/boot/d
> ts/rockchip/rk356x.dtsi#L1539 [2]
> https://code.ffmpeg.org/Kwiboo/FFmpeg/commits/branch/v4l2request-v3 [3]
> https://github.com/chewitt/linux/commits/rockchip-6.19.y
>
> Christian Hewitt (3):
> media: dt-bindings: rockchip: Add RK3568 Video Decoder bindings
> media: rkvdec: Add support for the VDPU346 variant
> arm64: dts: rockchip: Add the vdpu346 Video Decoders on RK356X
>
> .../bindings/media/rockchip,vdec.yaml | 2 +
> arch/arm64/boot/dts/rockchip/rk356x-base.dtsi | 49 +++++++++
> .../media/platform/rockchip/rkvdec/rkvdec.c | 103 ++++++++++++++++++
> 3 files changed, 154 insertions(+)
I tested this patch series on my RK3566 board with my own test videos and BBB
(1080p60 and 4k30) using mpv with [1] patchset.
The command I used was:
`mpv --vo=dmabuf-wayland --hwdec=v4l2request input_file.mp4`
Both H264 and HEVC plays with minor framedrops (which to me isn't noticeable).
You can add my Tested-by:
Tested-by: Dang Huynh <dang.huynh@mainlining.org>
[1]: https://github.com/mpv-player/mpv/pull/14690
Best regards,
Dang
next prev parent reply other threads:[~2026-01-03 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 11:31 [PATCH v2 0/3] media: rockchip: rkvdec: add support for the VDPU346 variant Christian Hewitt
2025-12-26 11:31 ` [PATCH v2 1/3] media: dt-bindings: rockchip: Add RK3568 Video Decoder bindings Christian Hewitt
2025-12-26 11:31 ` [PATCH v2 2/3] media: rkvdec: Add support for the VDPU346 variant Christian Hewitt
2025-12-26 12:00 ` Diederik de Haas
2025-12-26 12:25 ` Christian Hewitt
2026-01-05 17:42 ` Nicolas Dufresne
2025-12-26 11:31 ` [PATCH v2 3/3] arm64: dts: rockchip: Add the vdpu346 Video Decoders on RK356X Christian Hewitt
2026-01-03 20:10 ` Dang Huynh [this message]
2026-03-08 21:40 ` [PATCH v2 0/3] media: rockchip: rkvdec: add support for the VDPU346 variant Nicolas Dufresne
2026-03-14 14:19 ` Diederik de Haas
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=8993014.lOV4Wx5bFT@melttower \
--to=dang.huynh@mainlining.org \
--cc=amadeus@jmu.edu.cn \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dsimic@manjaro.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--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=mchehab@kernel.org \
--cc=olivier.crete@collabora.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox