From: Christian Hewitt <christianshewitt@gmail.com>
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
Subject: [PATCH v2 1/3] media: dt-bindings: rockchip: Add RK3568 Video Decoder bindings
Date: Fri, 26 Dec 2025 11:31:38 +0000 [thread overview]
Message-ID: <20251226113140.573759-2-christianshewitt@gmail.com> (raw)
In-Reply-To: <20251226113140.573759-1-christianshewitt@gmail.com>
The video decoder in RK356X (vdpu346) is described in the same way as
the one in RK3588 (vdpu381). A new compatible is added as the decoder
capabilities are a subset of the vdpu381 capabilities.
Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
---
Documentation/devicetree/bindings/media/rockchip,vdec.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/rockchip,vdec.yaml b/Documentation/devicetree/bindings/media/rockchip,vdec.yaml
index 809fda45b3bd..656ceb1f116e 100644
--- a/Documentation/devicetree/bindings/media/rockchip,vdec.yaml
+++ b/Documentation/devicetree/bindings/media/rockchip,vdec.yaml
@@ -18,6 +18,7 @@ properties:
oneOf:
- const: rockchip,rk3288-vdec
- const: rockchip,rk3399-vdec
+ - const: rockchip,rk3568-vdec
- const: rockchip,rk3576-vdec
- const: rockchip,rk3588-vdec
- items:
@@ -107,6 +108,7 @@ allOf:
compatible:
contains:
enum:
+ - rockchip,rk3568-vdec
- rockchip,rk3576-vdec
- rockchip,rk3588-vdec
then:
--
2.34.1
next prev parent reply other threads:[~2025-12-26 11:31 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 ` Christian Hewitt [this message]
2025-12-26 11:31 ` [PATCH v2 2/3] media: rkvdec: Add " 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 ` [PATCH v2 0/3] media: rockchip: rkvdec: add support for the VDPU346 variant Dang Huynh
2026-03-08 21:40 ` 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=20251226113140.573759-2-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=amadeus@jmu.edu.cn \
--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