All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	gabriel@unseen.is, Marek Szyprowski <m.szyprowski@samsung.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: Really fix choppy sound because of wrong residue calculation
Date: Tue, 7 Jul 2015 09:30:50 +0530	[thread overview]
Message-ID: <20150707040050.GF11002@localhost> (raw)
In-Reply-To: <1434376809-8029-1-git-send-email-k.kozlowski.k@gmail.com>

On Mon, Jun 15, 2015 at 11:00:09PM +0900, Krzysztof Kozlowski wrote:
> When pl330 driver was used during sound playback, after some time or
> after a number of plays the sound became choppy or totally noisy. For
> example on Odroid XU3 board the first four executions of aplay with
> small WAVE worked fine, but fifth was unrecognizable with errors:
> 	$ aplay /usr/share/sounds/alsa/Front_Right.wava
> 	underrun!!! (at least 0.095 ms long)
> 
> Issue was caused by wrong residue reported by pl330 driver to
> pcm_dmaengine for its cyclic dma transfers.
> 
> The pl330_tx_status(), residue reporting function, used a "last" flag in
> a descriptor to indicate that there is no more data to send.
> 
> The pl330_tx_submit() iterated over descriptors trying to remove this
> flag from them and then mark last descriptor as "last".  However when
> iterating it actually removed the flag not from descriptors but always
> from last of it (and then reset it). Thus effectively once some
> descriptor was marked as last, then it stayed like this forever causing
> residue to be reported too low.

Applied, thanks

-- 
~Vinod


      parent reply	other threads:[~2015-07-07  3:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 14:00 [PATCH] dmaengine: pl330: Really fix choppy sound because of wrong residue calculation Krzysztof Kozlowski
2015-06-22  2:14 ` Krzysztof Kozłowski
2015-06-22  2:14   ` Krzysztof Kozłowski
2015-06-30  4:14   ` Vinod Koul
2015-06-30  4:51     ` Krzysztof Kozłowski
2015-06-30  7:01       ` Lars-Peter Clausen
2015-06-30  7:57         ` Krzysztof Kozłowski
2015-07-07  4:00 ` Vinod Koul [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=20150707040050.GF11002@localhost \
    --to=vinod.koul@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gabriel@unseen.is \
    --cc=k.kozlowski.k@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=stable@vger.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 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.