All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Patrick Doyle <wpdster@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0p:0, pos = 32768, buffer size = 32768 , period size = 2048
Date: Mon, 06 Sep 2010 19:35:55 +0200	[thread overview]
Message-ID: <4C85267B.40002@ladisch.de> (raw)
In-Reply-To: <AANLkTi=nJMA_7Y0kjqZgcFy5AwJkbZM_D0rnMdVk3j6v@mail.gmail.com>

Patrick Doyle wrote:
> On Mon, Sep 6, 2010 at 3:16 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Patrick Doyle wrote:
> > > pos = 32768, buffer size = 32768
> >
> > This means that the driver's pointer callback returned a position that
> > is outside the buffer; in this case, the position is just after the end
> > of the buffer.
> 
> OK, so I should go trace down how and when the driver invokes that
> callback.

That callback is invoked by the ALSA framework.
The callback itself is buggy.

> Hmmm... any tips on where I might start that journey, given that this
> driver is an SoC driver?

bf5xx_pcm_pointer() in soc/blackfin/bf5xx-i2s-pcm.c calls
sport_curr_offset_tx() in soc/blackfin/bf5xx-sport.c, which just calls
get_dma_curr_addr().

I'd guess that the end of the buffer is considered a valid address by
the Blackfin's DMA unit, so the driver has to check for that and wrap
it around to zero.


Regards,
Clemens

      parent reply	other threads:[~2010-09-06 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 18:28 ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0p:0, pos = 32768, buffer size = 32768 , period size = 2048 Patrick Doyle
2010-09-06  7:16 ` Clemens Ladisch
     [not found]   ` <AANLkTi=nJMA_7Y0kjqZgcFy5AwJkbZM_D0rnMdVk3j6v@mail.gmail.com>
2010-09-06 17:35     ` Clemens Ladisch [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=4C85267B.40002@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=wpdster@gmail.com \
    /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 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.