public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Detlev Casanova <detlev.casanova@collabora.com>
To: Jianfeng Liu <liujianfeng1994@gmail.com>
Cc: heiko@sntech.de, kernel@collabora.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rockchip@lists.infradead.org, mchehab@kernel.org,
	nicolas.dufresne@collabora.com, nicolas.frattaroli@collabora.com
Subject: Re: [PATCH 00/12] media: rkvdec: Add support for VDPU381 and VDPU383
Date: Mon, 14 Jul 2025 09:35:19 -0400	[thread overview]
Message-ID: <2229133.irdbgypaU6@trenzalore> (raw)
In-Reply-To: <20250713142514.56742-1-liujianfeng1994@gmail.com>

Hi Jianfeng,

On Sunday, 13 July 2025 10:25:14 EDT Jianfeng Liu wrote:
> Hi,
> 
> On Tue,  8 Jul 2025 11:19:33 -0400, Detlev Casanova wrote:
> >As there is a considerable part of the code that can be shared with the
> >already supported rkvdec decoder driver, the support for these variants
> >is added here rather than writing a new driver.
> 
> I have tested the new series on rk3588 and rk3399 with chromium. Since the
> HEVC decoder need EXT_SPS_RPS related patches, I ony test the H264 decoder.
> There are two issues:
> 
> 1, The decoder max size is detected 1920x1088, which should be the fallback
> size when queryig VIDIOC_ENUM_FRAMESIZES[1].

From the linked code, the max size is hard coded to 1920x1088.
The driver sets the frame size type to V4L2_FRMSIZE_TYPE_CONTINUOUS, so the 
snippet you pointed to doesn't update the values for max/min. See [2] for the 
discussion about using V4L2_FRMSIZE_TYPE_CONTINUOUS.

> 2, Playing H264 videos ends up with green screen.

Can you elaborate a bit ? What videos ?
Is that on both SoCs ?
Is there any logs in dmesg ?

> These above issues don't happen with the old rkvdec2 series.
> 
> [1]
> https://github.com/chromium/chromium/blob/138.0.7204.92/media/gpu/v4l2/v4l2
> _utils.cc#L520-L533

[2] https://lore.kernel.org/all/c7882f94-e2cb-4023-a53e-87ebc8fa3460@gmail.com/

Regards,
Detlev






  reply	other threads:[~2025-07-14 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 15:19 [PATCH 00/12] media: rkvdec: Add support for VDPU381 and VDPU383 Detlev Casanova
2025-07-08 15:19 ` [PATCH 01/12] media: rkvdec: Switch to using structs instead of writel Detlev Casanova
2025-07-08 15:19 ` [PATCH 02/12] media: rkvdec: Move cabac table to its own source file Detlev Casanova
2025-07-08 15:19 ` [PATCH 03/12] media: rkvdec: Use structs to represent the HW RPS Detlev Casanova
2025-07-08 15:19 ` [PATCH 04/12] media: rkvdec: Move h264 functions to common file Detlev Casanova
2025-07-08 15:19 ` [PATCH 05/12] media: rkvdec: Add per variant configuration Detlev Casanova
2025-07-08 15:19 ` [PATCH 06/12] media: rkvdec: Add RCB and SRAM support Detlev Casanova
2025-07-08 15:19 ` [PATCH 07/12] media: rkvdec: Support per-variant interrupt handler Detlev Casanova
2025-07-08 15:19 ` [PATCH 08/12] media: rkvdec: Enable all clocks without naming them Detlev Casanova
2025-07-08 15:19 ` [PATCH 09/12] media: rkvdec: Add H264 support for the VDPU381 variant Detlev Casanova
2025-07-08 15:19 ` [PATCH 10/12] media: rkvdec: Add H264 support for the VDPU383 variant Detlev Casanova
2025-07-08 15:19 ` [PATCH 12/12] media: rkvdec: Add HEVC " Detlev Casanova
2025-07-13 14:25 ` Re:[PATCH 00/12] media: rkvdec: Add support for VDPU381 and VDPU383 Jianfeng Liu
2025-07-14 13:35   ` Detlev Casanova [this message]
2025-07-14 14:46     ` [PATCH " Jianfeng Liu
2025-07-18  9:37       ` Jianfeng Liu
2025-07-28 20:22         ` Nicolas Dufresne

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=2229133.irdbgypaU6@trenzalore \
    --to=detlev.casanova@collabora.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.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=liujianfeng1994@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=nicolas.frattaroli@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