LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH] media: coda: Keep metas sync with hardware fifo
Date: Fri, 12 Nov 2021 10:30:29 +0100	[thread overview]
Message-ID: <5edb9e93f82ba848bde1e17c8a0cf47847f66e17.camel@pengutronix.de> (raw)
In-Reply-To: <4247f8c1-496b-4026-a328-284a495b88f3@collabora.com>

Hi Benjamin,

On Fri, 2021-11-12 at 09:36 +0100, Benjamin Gaignard wrote:
> Le 11/11/2021 à 18:03, Philipp Zabel a écrit :
> > Hi Benjamin,
> > 
> > On Mon, 2021-11-08 at 15:24 +0100, Benjamin Gaignard wrote:
> > > After updating the output fifo position be sure that metas are also
> > > synchronised with this position.
> > > 
> > > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > > ---
> > >   drivers/media/platform/coda/coda-bit.c | 6 ++++++
> > >   1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/drivers/media/platform/coda/coda-bit.c b/drivers/media/platform/coda/coda-bit.c
> > > index c484c008ab02..28c56286b0de 100644
> > > --- a/drivers/media/platform/coda/coda-bit.c
> > > +++ b/drivers/media/platform/coda/coda-bit.c
> > > @@ -2315,6 +2315,12 @@ static void coda_finish_decode(struct coda_ctx *ctx)
> > >   	/* Update kfifo out pointer from coda bitstream read pointer */
> > >   	coda_kfifo_sync_from_device(ctx);
> > > 
> > > +	/*
> > > +	 * After updating the read pointer, we need to check if
> > > +	 * any metas are consumed and should be released.
> > > +	 */
> > > +	coda_decoder_drop_used_metas(ctx);
> > > +
> > This doesn't look right. If you drop all metas seen by the decoder right
> > away, they can't be copied into the decoded picture's meta slot later in
> > this function. I'd expect you run into the "empty timestamp list!"
> > errors if you do this.
> 
> Hi Philipp,
> 
> I don't run into the "empty timestamp list!" errors.
> The only case I have seen metas been dropped here it is when
> an invalid/incomplete frame has been send into the decoder.
> When that happens I don't see any interrupt or error message but
> the erroneous frame stay in the list.
> If that occur 4 times (I'm using CODA 960) then the decoder hang.
> Dropping the metas at this moment solve this problem.
> 
> Maybe you can guide me to a better solution ?

Hmm, the current code silently assumes that in the good case there's
exactly one used meta (it just picks the first one from the list if
decoded_idx is set).

We could list_cut_before() the used metas into a local list, let the
decoded_idx code pick the timestamp from that list, and then drop the
whole local list of used metas on return from coda_finish_decode().

regards
Philipp

      reply	other threads:[~2021-11-12  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 14:24 [PATCH] media: coda: Keep metas sync with hardware fifo Benjamin Gaignard
2021-11-11 17:03 ` Philipp Zabel
2021-11-12  8:36   ` Benjamin Gaignard
2021-11-12  9:30     ` Philipp Zabel [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=5edb9e93f82ba848bde1e17c8a0cf47847f66e17.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=benjamin.gaignard@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).