From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: linux-media@vger.kernel.org
Cc: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Subject: [PATCH v1 03/03]: dt-bindings: media: rockchip-vpu: Add RK3568 compatible
Date: Sun, 13 Feb 2022 18:13:52 +0100 [thread overview]
Message-ID: <20220213171349.3924782-3-piotr.oniszczuk@gmail.com> (raw)
In-Reply-To: <20220213171349.3924782-1-piotr.oniszczuk@gmail.com>
From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
RK356x has Hantro G1 video decoder capable to decode MPEG2/H.264/VP9
video formats.
This patch adds RK3568 compatible in rockchip-vpu dt-bindings.
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>
---
Documentation/devicetree/bindings/media/rockchip-vpu.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
index bacb60a34989..6cc4d3e5a61d 100644
--- a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
+++ b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
@@ -23,6 +23,7 @@ properties:
- rockchip,rk3328-vpu
- rockchip,rk3399-vpu
- rockchip,px30-vpu
+ - rockchip,rk3568-vpu
- items:
- const: rockchip,rk3188-vpu
- const: rockchip,rk3066-vpu
--
2.29.2
prev parent reply other threads:[~2022-02-13 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 17:13 [PATCH v1 01/03]: media: hantro: Add support for Hantro G1 on RK356x Piotr Oniszczuk
2022-02-13 17:13 ` [PATCH v1 02/03]: arm64: dts: rk356x.dtsi: " Piotr Oniszczuk
2022-02-14 11:51 ` Ezequiel Garcia
2022-02-13 17:13 ` Piotr Oniszczuk [this message]
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=20220213171349.3924782-3-piotr.oniszczuk@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=linux-media@vger.kernel.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