[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240618121329.79936-1-liujianfeng1994@gmail.com>
Date: Tue, 18 Jun 2024 20:13:29 +0800
From: Jianfeng Liu <liujianfeng1994@...il.com>
To: detlev.casanova@...labora.com
Cc: alchark@...il.com,
andy.yan@...k-chips.com,
conor+dt@...nel.org,
cristian.ciocaltea@...labora.com,
devicetree@...r.kernel.org,
didi.debian@...ow.org,
dsimic@...jaro.org,
gregkh@...uxfoundation.org,
heiko@...ech.de,
krzk+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org,
linux-rockchip@...ts.infradead.org,
linux-staging@...ts.linux.dev,
liujianfeng1994@...il.com,
mchehab@...nel.org,
nicolas@...fresne.ca,
robh@...nel.org,
sebastian.reichel@...labora.com
Subject: Re: [PATCH 1/3] media: rockchip: Introduce the rkvdec2 driver
Hi Detlev,
On Fri, 14 Jun 2024 21:56:27 -0400, Detlev Casanova wrote:
>+ .frmsize = {
>+ .min_width = 16,
>+ .max_width = 65520,
>+ .step_width = 16,
>+ .min_height = 16,
>+ .max_height = 65520,
>+ .step_height = 16,
>+ },
I think the min/max width/height are incorrect. From rockchip's TRM V1.0
Part1 page 374, supported image size is 64x64 to 65472x65472. And my
chromium can't use rkvdec2 because min width/height are set to 16, which
will cause error at here in rkvdec2_h264_validate_sps:
>+ if (width > ctx->coded_fmt.fmt.pix_mp.width ||
>+ height > ctx->coded_fmt.fmt.pix_mp.height)
>+ return -EINVAL;
width is 16, height is 32 while ctx->coded_fmt.fmt.pix_mp.width and
ctx->coded_fmt.fmt.pix_mp.height are both 16.
After changing them to 64 my chromium can use rkvdec2 to decode h264
videos now.
Anyway many thanks to your amazing work!
Best regards,
Jianfeng
Powered by blists - more mailing lists