From: Jonas Karlman <jonas@kwiboo.se> To: Ezequiel Garcia <ezequiel@collabora.com>, linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Tomasz Figa <tfiga@chromium.org>, kernel@collabora.com, Heiko Stuebner <heiko@sntech.de>, Hans Verkuil <hverkuil@xs4all.nl>, Alexandre Courbot <acourbot@chromium.org>, Jeffrey Kardatzke <jkardatzke@chromium.org>, gustavo.padovan@collabora.com, Boris Brezillon <boris.brezillon@collabora.com> Subject: Re: [PATCH v3 3/3] media: rkvdec: Add the VP9 backend Date: Fri, 08 May 2020 11:21:08 +0000 (UTC) [thread overview] Message-ID: <4ac628c6-0845-7bca-2c1a-4d6ef2a4019f@kwiboo.se> (raw) In-Reply-To: <20200505134110.3435-4-ezequiel@collabora.com> On 2020-05-05 15:41, Ezequiel Garcia wrote: > From: Boris Brezillon <boris.brezillon@collabora.com> > > The Rockchip VDEC supports VP9 profile 0 up to 4096x2304@30fps. Add > a backend for this new format. > > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com> I have tested this series on a Rock Pi 4 RK3399 device using the ffmpeg vp9 request api hwaccel at [1]. Decoding up to 3840x2160@30fps media is working great. (frame scaling was not tested or fully implemented in ffmpeg hwaccel) Tested-by: Jonas Karlman <jonas@kwiboo.se> [1] https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-4.2.2 Regards, Jonas > --- > drivers/staging/media/rkvdec/Makefile | 2 +- > drivers/staging/media/rkvdec/rkvdec-vp9.c | 1577 +++++++++++++++++++++ > drivers/staging/media/rkvdec/rkvdec.c | 56 +- > drivers/staging/media/rkvdec/rkvdec.h | 6 + > 4 files changed, 1637 insertions(+), 4 deletions(-) > create mode 100644 drivers/staging/media/rkvdec/rkvdec-vp9.c > [...]
WARNING: multiple messages have this Message-ID (diff)
From: Jonas Karlman <jonas-uIzNG4q0ceqzQB+pC5nmwQ@public.gmane.org> To: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>, linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>, Alexandre Courbot <acourbot-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>, Tomasz Figa <tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>, Hans Verkuil <hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>, gustavo.padovan-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org, Boris Brezillon <boris.brezillon-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>, Jeffrey Kardatzke <jkardatzke-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>, kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org Subject: Re: [PATCH v3 3/3] media: rkvdec: Add the VP9 backend Date: Fri, 08 May 2020 11:21:08 +0000 (UTC) [thread overview] Message-ID: <4ac628c6-0845-7bca-2c1a-4d6ef2a4019f@kwiboo.se> (raw) In-Reply-To: <20200505134110.3435-4-ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> On 2020-05-05 15:41, Ezequiel Garcia wrote: > From: Boris Brezillon <boris.brezillon-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> > > The Rockchip VDEC supports VP9 profile 0 up to 4096x2304@30fps. Add > a backend for this new format. > > Signed-off-by: Boris Brezillon <boris.brezillon-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> > Signed-off-by: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> I have tested this series on a Rock Pi 4 RK3399 device using the ffmpeg vp9 request api hwaccel at [1]. Decoding up to 3840x2160@30fps media is working great. (frame scaling was not tested or fully implemented in ffmpeg hwaccel) Tested-by: Jonas Karlman <jonas-uIzNG4q0ceqzQB+pC5nmwQ@public.gmane.org> [1] https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-4.2.2 Regards, Jonas > --- > drivers/staging/media/rkvdec/Makefile | 2 +- > drivers/staging/media/rkvdec/rkvdec-vp9.c | 1577 +++++++++++++++++++++ > drivers/staging/media/rkvdec/rkvdec.c | 56 +- > drivers/staging/media/rkvdec/rkvdec.h | 6 + > 4 files changed, 1637 insertions(+), 4 deletions(-) > create mode 100644 drivers/staging/media/rkvdec/rkvdec-vp9.c > [...]
next prev parent reply other threads:[~2020-05-08 11:26 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-05 13:41 [PATCH v3 0/3] media: rkvdec: Add a VP9 backend Ezequiel Garcia 2020-05-05 13:41 ` [PATCH v3 1/3] media: rkvdec: Fix .buf_prepare Ezequiel Garcia 2020-05-05 13:56 ` Tomasz Figa 2020-05-05 13:59 ` Ezequiel Garcia 2020-05-05 14:05 ` Tomasz Figa 2020-05-05 14:27 ` Ezequiel Garcia 2020-05-13 23:38 ` Nicolas Dufresne 2020-05-14 14:50 ` Nicolas Dufresne 2020-05-05 13:41 ` [PATCH v3 2/3] media: uapi: Add VP9 stateless decoder controls Ezequiel Garcia 2020-05-08 10:27 ` Hans Verkuil 2020-05-08 12:28 ` Ezequiel Garcia 2020-05-08 13:16 ` Hans Verkuil 2020-05-11 12:17 ` Nicolas Dufresne 2020-05-05 13:41 ` [PATCH v3 3/3] media: rkvdec: Add the VP9 backend Ezequiel Garcia 2020-05-08 10:34 ` Hans Verkuil 2020-05-08 16:26 ` Ezequiel Garcia 2020-05-08 16:56 ` Tomasz Figa 2020-05-11 13:26 ` Ezequiel Garcia 2020-05-08 11:21 ` Jonas Karlman [this message] 2020-05-08 11:21 ` Jonas Karlman
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=4ac628c6-0845-7bca-2c1a-4d6ef2a4019f@kwiboo.se \ --to=jonas@kwiboo.se \ --cc=acourbot@chromium.org \ --cc=boris.brezillon@collabora.com \ --cc=ezequiel@collabora.com \ --cc=gustavo.padovan@collabora.com \ --cc=heiko@sntech.de \ --cc=hverkuil@xs4all.nl \ --cc=jkardatzke@chromium.org \ --cc=kernel@collabora.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=tfiga@chromium.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.