From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, ezequiel@vanguardiasur.com.ar,
p.zabel@pengutronix.de, mchehab@kernel.org, sfr@canb.auug.org.au,
liujianfeng1994@gmail.com
Subject: [PATCH v5 0/2] Add hantro g1 video decoder support for RK3588
Date: Sat, 13 Apr 2024 14:46:06 +0800 [thread overview]
Message-ID: <20240413064608.788561-1-liujianfeng1994@gmail.com> (raw)
This is the v5 version of this series adding hantro g1 video decoder
support for RK3588.
RK3588 has Hantro G1 video decoder known as VDPU121 in TRM of RK3588 which
is capable to decode MPEG2/H.264/VP8 up to 1920x1088. This vpu ip is also
found in RK3568.
Test results from fluster can be found from thread of v3[1].
Changes in v5:
- Add missing interrupt-names to devicetree node
- Rebase devicetree patch based on next-20240412
- Link to v4: https://lore.kernel.org/all/20240316071100.2419369-1-liujianfeng1994@gmail.com/
[1]https://lore.kernel.org/all/20240118080602.9028-1-liujianfeng1994@gmail.com/
Jianfeng Liu (2):
arm64: dts: rockchip: Add Hantro G1 VPU support for RK3588
dt-bindings: media: rockchip-vpu: Add rk3588 vdpu121 compatible string
.../bindings/media/rockchip-vpu.yaml | 3 +++
arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 21 +++++++++++++++++++
2 files changed, 24 insertions(+)
--
2.34.1
next reply other threads:[~2024-04-13 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 6:46 Jianfeng Liu [this message]
2024-04-13 6:46 ` [PATCH v5 1/2] arm64: dts: rockchip: Add Hantro G1 VPU support for RK3588 Jianfeng Liu
2024-04-14 18:36 ` Sebastian Reichel
2024-04-13 6:46 ` [PATCH v5 2/2] dt-bindings: media: rockchip-vpu: Add rk3588 vdpu121 compatible string Jianfeng Liu
2024-04-13 7:44 ` Krzysztof Kozlowski
2024-04-13 15:57 ` Jianfeng Liu
2024-04-18 9:19 ` Diederik de Haas
2024-04-18 16:08 ` Conor Dooley
2024-04-14 18:37 ` Sebastian Reichel
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=20240413064608.788561-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).