From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Cc: linux-media@vger.kernel.org, Linux-rockchip@lists.infradead.org,
heiko@sntech.de, hverkuil@xs4all.nl
Subject: Re: [PATCH v2 2/3] arm64: dts: rockchip: Add VPU support for RK3568/RK3566
Date: Sun, 20 Mar 2022 09:37:31 -0300 [thread overview]
Message-ID: <YjcgC9HZeDQX1sNJ@eze-laptop> (raw)
In-Reply-To: <20220214212955.1178947-2-piotr.oniszczuk@gmail.com>
On Mon, Feb 14, 2022 at 10:29:54PM +0100, Piotr Oniszczuk wrote:
> From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
>
> RK356x has Hantro G1 video decoder capable to decode MPEG2/H.264/VP8
> video formats.
>
> This patch enables RK356x video decoder in RK356x device-tree
> include.
>
> Tested on [1] with FFmpeg v4l2_request code taken from [2]
> with MPEG2, H.642 and VP8 samples with results [3].
>
> [1] https://github.com/warpme/minimyth2
> [2] https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/multimedia/ffmpeg/patches/v4l2-request/ffmpeg-001-v4l2-request.patch
> [3] https://github.com/warpme/minimyth2/blob/master/video-test-summary.txt
>
> Signed-off-by: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Thanks,
Ezequiel
> ---
> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> index a68033a23975..33ecaafa8cb7 100644
> --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> @@ -390,6 +390,26 @@ power-domain@RK3568_PD_RKVENC {
> };
> };
>
> + vpu: video-codec@fdea0400 {
> + compatible = "rockchip,rk3568-vpu";
> + reg = <0x0 0xfdea0000 0x0 0x800>;
> + interrupts = <GIC_SPI 139 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru ACLK_VPU>, <&cru HCLK_VPU>;
> + clock-names = "aclk", "hclk";
> + iommus = <&vdpu_mmu>;
> + power-domains = <&power RK3568_PD_VPU>;
> + };
> +
> + vdpu_mmu: iommu@fdea0800 {
> + compatible = "rockchip,rk3568-iommu";
> + reg = <0x0 0xfdea0800 0x0 0x40>;
> + interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>;
> + clock-names = "aclk", "iface";
> + clocks = <&cru ACLK_VPU>, <&cru HCLK_VPU>;
> + power-domains = <&power RK3568_PD_VPU>;
> + #iommu-cells = <0>;
> + };
> +
> sdmmc2: mmc@fe000000 {
> compatible = "rockchip,rk3568-dw-mshc", "rockchip,rk3288-dw-mshc";
> reg = <0x0 0xfe000000 0x0 0x4000>;
> --
> 2.29.2
>
next prev parent reply other threads:[~2022-03-20 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 21:29 [PATCH v2 1/3] media: hantro: Add support for Hantro G1 on RK356x Piotr Oniszczuk
2022-02-14 21:29 ` [PATCH v2 2/3] arm64: dts: rockchip: Add VPU support for RK3568/RK3566 Piotr Oniszczuk
2022-03-20 12:37 ` Ezequiel Garcia [this message]
2022-07-25 16:29 ` Ezequiel Garcia
2022-02-14 21:29 ` [PATCH v2 3/3] dt-bindings: media: rockchip-vpu: Add RK3568 compatible Piotr Oniszczuk
2022-03-20 12:39 ` Ezequiel Garcia
2022-04-21 11:13 ` Ezequiel Garcia
2022-03-20 12:35 ` [PATCH v2 1/3] media: hantro: Add support for Hantro G1 on RK356x Ezequiel Garcia
2022-09-09 23:10 ` (subset) " Heiko Stuebner
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=YjcgC9HZeDQX1sNJ@eze-laptop \
--to=ezequiel@vanguardiasur.com.ar \
--cc=Linux-rockchip@lists.infradead.org \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=piotr.oniszczuk@gmail.com \
/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