From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
ezequiel@vanguardiasur.com.ar, p.zabel@pengutronix.de,
mchehab@kernel.org, heiko@sntech.de, hverkuil-cisco@xs4all.nl
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] media: verisilicon: av1: Fix reference video buffer pointer assignment
Date: Fri, 13 Sep 2024 10:52:26 -0400 [thread overview]
Message-ID: <2042cabf9d8d2ca7faea485d2b5d21aa438a63d3.camel@ndufresne.ca> (raw)
In-Reply-To: <6c6e00fd-334c-41ae-963c-eeffb368b727@collabora.com>
Le mercredi 11 septembre 2024 à 10:36 +0200, Benjamin Gaignard a écrit :
> Le 10/09/2024 à 21:44, Nicolas Dufresne a écrit :
> > Hi,
> >
> > Le mardi 10 septembre 2024 à 14:10 +0000, Benjamin Gaignard a écrit :
> > > Always get new destination buffer for reference frame because nothing
> > > garanty the one set previously is still valid or unused.
> > Mind documenting here which tests got fixed with this change ?
>
> Only one from chromium test suite:
> https://chromium.googlesource.com/chromium/src/media/+/refs/heads/main/test/data/test-25fps.av1.ivf
>
> Fluster AV1 score remains unchanged.
We already integrated a lot of chromium tests in Fluster, would make sense to
include some more. Was this one missed ? or added later ?
>
> >
> > > Fixes: 727a400686a2 ("media: verisilicon: Add Rockchip AV1 decoder")
> > > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > > ---
> > > .../media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c | 3 +--
> > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c b/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c
> > > index 372dfcd0fcd9..2b9a1047479c 100644
> > > --- a/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c
> > > +++ b/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c
> > > @@ -161,8 +161,7 @@ static int rockchip_vpu981_av1_dec_frame_ref(struct hantro_ctx *ctx,
> > > av1_dec->frame_refs[i].timestamp = timestamp;
> > > av1_dec->frame_refs[i].frame_type = frame->frame_type;
> > > av1_dec->frame_refs[i].order_hint = frame->order_hint;
> > > - if (!av1_dec->frame_refs[i].vb2_ref)
> > > - av1_dec->frame_refs[i].vb2_ref = hantro_get_dst_buf(ctx);
> > > + av1_dec->frame_refs[i].vb2_ref = hantro_get_dst_buf(ctx);
> > Good catch, would still be nice to improve the commit message.
> >
> > Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> >
> > >
> > > for (j = 0; j < V4L2_AV1_TOTAL_REFS_PER_FRAME; j++)
> > > av1_dec->frame_refs[i].order_hints[j] = frame->order_hints[j];
> >
prev parent reply other threads:[~2024-09-13 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 14:10 Benjamin Gaignard
2024-09-10 19:44 ` Nicolas Dufresne
2024-09-11 8:36 ` Benjamin Gaignard
2024-09-13 14:52 ` Nicolas Dufresne [this message]
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=2042cabf9d8d2ca7faea485d2b5d21aa438a63d3.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=benjamin.gaignard@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil-cisco@xs4all.nl \
--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=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
/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®