From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: mripard@kernel.org, paul.kocialkowski@bootlin.com,
Ezequiel Garcia <ezequiel@collabora.com>
Cc: devel@driverdev.osuosl.org,
Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
hverkuil@xs4all.nl, wens@csie.org, mchehab@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: Re: [PATCH v3] media: cedrus: Add support for VP8 decoding
Date: Fri, 27 Nov 2020 00:40:31 +0100 [thread overview]
Message-ID: <2282897.HYN9I3zZbb@kista> (raw)
In-Reply-To: <1496f292eadc62a3ab585a89cf9b997ce4a1d799.camel@collabora.com>
Hi!
Dne petek, 27. november 2020 ob 00:21:11 CET je Ezequiel Garcia napisal(a):
> Hi Jernej, Emmanuel,
>
> Thanks for the patch.
>
> On Tue, 2020-11-10 at 23:35 +0100, Jernej Skrabec wrote:
> > VP8 in Cedrus shares same engine as H264.
> >
> > Note that it seems necessary to call bitstream parsing functions,
> > to parse frame header, otherwise decoded image is garbage. This is
> > contrary to what is driver supposed to do. However, values are not
> > really used, so this might be acceptable. It's possible that bitstream
> > parsing functions set some internal VPU state, which is later necessary
> > for proper decoding. Biggest suspect is "VP8 probs update" trigger.
> >
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> > [addressed issues from reviewer]
> > Signed-off-by: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
> > ---
> > Changes in v3:
> > - addressed comments from Ezequiel Garcia - new comments,
> > using new macros from VP8 UAPI, new function for waiting
> > on bit to be set
> > Changes in v2:
> > - rebased on top of current linux-media master branch
> >
> > NOTE: This now depends on following patch:
> > https://patchwork.linuxtv.org/project/linux-media/patch/
20201108202021.4187-1-linkmauve@linkmauve.fr/
> >
>
> The patch looks fairly good, so let's wait and see
> what Hans, Paul and Maxime think about it.
>
> FWIW, my humble Reviewed-by: Ezequiel Garcia <ezequiel@collabora.com>
Thanks!
>
> It would be good to make sure this doesn't regress
> v4l2-compliance, or cause some regression in decoding.
I didn't include v4l2-compliance here, but it was in previous revisions. This
revision has just cosmetics. Not sure how it could cause any regression since
it's pretty standalone.
>
> Not really a blocker to merge this, but I'm thinking
> that now that we have Fluster for conformance testing,
> we could add the VP8 vectors and use them against
> Cedrus and Hantro:
>
> https://chromium.googlesource.com/webm/vp8-test-vectors/+/refs/heads/master
I tested VP8 test vectors with initial version of this decoder by hand and all
videos were properly decoded as far as I can tell. But automated testing is
always welcome.
Best regards,
Jernej
>
> Thanks,
> Ezequiel
>
> > drivers/staging/media/sunxi/cedrus/Makefile | 3 +-
> > drivers/staging/media/sunxi/cedrus/cedrus.c | 8 +
> > drivers/staging/media/sunxi/cedrus/cedrus.h | 24 +
> > .../staging/media/sunxi/cedrus/cedrus_dec.c | 5 +
> > .../staging/media/sunxi/cedrus/cedrus_hw.c | 2 +
> > .../staging/media/sunxi/cedrus/cedrus_regs.h | 80 ++
> > .../staging/media/sunxi/cedrus/cedrus_video.c | 9 +
> > .../staging/media/sunxi/cedrus/cedrus_vp8.c | 907 ++++++++++++++++++
> > 8 files changed, 1037 insertions(+), 1 deletion(-)
> > create mode 100644 drivers/staging/media/sunxi/cedrus/cedrus_vp8.c
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-26 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 22:35 [PATCH v3] media: cedrus: Add support for VP8 decoding Jernej Skrabec
2020-11-26 23:21 ` Ezequiel Garcia
2020-11-26 23:40 ` Jernej Škrabec [this message]
2020-11-26 23:39 ` Ezequiel Garcia
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=2282897.HYN9I3zZbb@kista \
--to=jernej.skrabec@siol.net \
--cc=devel@driverdev.osuosl.org \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linkmauve@linkmauve.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=wens@csie.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: 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