From: Jonas Karlman <jonas@kwiboo.se>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Detlev Casanova <detlev.casanova@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Alex Bee <knaerzche@gmail.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
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, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH v3 4/7] media: rkvdec: Add RK3288 variant
Date: Fri, 5 Sep 2025 16:19:22 +0000 [thread overview]
Message-ID: <20250905161942.3759717-5-jonas@kwiboo.se> (raw)
In-Reply-To: <20250905161942.3759717-1-jonas@kwiboo.se>
From: Alex Bee <knaerzche@gmail.com>
Add a RK3288 variant, a version of the Rockchip VDEC IP that only
support HEVC decoding.
Signed-off-by: Alex Bee <knaerzche@gmail.com>
Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
---
Changes in v3:
- Add num_regs field
- Collect r-b tag
Changes in v2:
- No change
---
drivers/media/platform/rockchip/rkvdec/rkvdec.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/media/platform/rockchip/rkvdec/rkvdec.c b/drivers/media/platform/rockchip/rkvdec/rkvdec.c
index 088ddfadf995..f8cbc7bcfa15 100644
--- a/drivers/media/platform/rockchip/rkvdec/rkvdec.c
+++ b/drivers/media/platform/rockchip/rkvdec/rkvdec.c
@@ -1221,6 +1221,11 @@ static void rkvdec_watchdog_func(struct work_struct *work)
}
}
+static const struct rkvdec_variant rk3288_rkvdec_variant = {
+ .num_regs = 68,
+ .capabilities = RKVDEC_CAPABILITY_HEVC,
+};
+
static const struct rkvdec_variant rk3399_rkvdec_variant = {
.num_regs = 78,
.capabilities = RKVDEC_CAPABILITY_HEVC |
@@ -1229,6 +1234,10 @@ static const struct rkvdec_variant rk3399_rkvdec_variant = {
};
static const struct of_device_id of_rkvdec_match[] = {
+ {
+ .compatible = "rockchip,rk3288-vdec",
+ .data = &rk3288_rkvdec_variant,
+ },
{
.compatible = "rockchip,rk3399-vdec",
.data = &rk3399_rkvdec_variant,
--
2.51.0
next prev parent reply other threads:[~2025-09-05 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 16:19 [PATCH v3 0/7] media: rkvdec: Add HEVC backend Jonas Karlman
2025-09-05 16:19 ` [PATCH v3 1/7] " Jonas Karlman
2025-09-05 16:19 ` [PATCH v3 2/7] media: rkvdec: Add variants support Jonas Karlman
2025-09-08 18:32 ` Detlev Casanova
2025-09-09 8:41 ` Jonas Karlman
2025-09-05 16:19 ` [PATCH v3 3/7] media: rkvdec: Implement capability filtering Jonas Karlman
2025-09-05 16:19 ` Jonas Karlman [this message]
2025-09-05 16:19 ` [PATCH v3 5/7] media: rkvdec: Disable QoS for HEVC and VP9 on RK3328 Jonas Karlman
2025-09-05 16:19 ` [PATCH v3 6/7] media: dt-bindings: rockchip,vdec: Add RK3288 compatible Jonas Karlman
2025-09-05 16:19 ` [PATCH v3 7/7] ARM: dts: rockchip: Add vdec node for RK3288 Jonas Karlman
2025-09-09 18:12 ` [PATCH v3 0/7] media: rkvdec: Add HEVC backend Detlev Casanova
2025-09-13 14:51 ` Diederik de Haas
2025-12-15 11:47 ` (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=20250905161942.3759717-5-jonas@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--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=nicolas.dufresne@collabora.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
all inboxes | Powered by JetHome®