From: Mark Brown <broonie@kernel.org>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: alsa-devel@alsa-project.org,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Padmavathi Venna <padma.v@samsung.com>,
Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Kukjin Kim <kgene.kim@samsung.com>,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible
Date: Thu, 5 Dec 2013 11:45:38 +0000 [thread overview]
Message-ID: <20131205114538.GO29268@sirena.org.uk> (raw)
In-Reply-To: <CAAgF-Bc3fOdJ3C-Jrmw-7Vxt_9QSJHEX5kWvCEyu_WBrsMDdEA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
On Thu, Dec 05, 2013 at 04:20:03PM +0530, Padma Venkat wrote:
> On Thu, Nov 28, 2013 at 5:23 PM, Mark Brown <broonie@kernel.org> wrote:
> > OK, so we can probably just reinitialise the dmaengine data after we
> > reset it? Like below
> Yes. That works well.
Great.
> As I forgot to add SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag, I was
> getting underrun error. After adding this flag audio playback is
> working fine for smaller files on smdk5420 with pl330 dma driver.
OK, there were some patches on the thread adding residue support to the
PL330 driver yesterday - hopefully those can get merged at some point
> Except for the crash due to NULL pointer dereference in secondary
> dai(I posted a patch for the same (ASoC: samsung: Initialize the
> dma_data for secondary dai)) you can add my
> Tested By: Padmavathi Venna <padma.v@samsung.com>
Excellent, thanks - I'd squashed in your change already. Like I say I'm
still concerned that we might need a fix for v3.13 since I can't
entirely see why the code works as-is.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-12-05 11:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 13:48 [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Mark Brown
2013-11-12 13:48 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
2013-11-26 5:25 ` [alsa-devel] " Padma Venkat
2013-11-26 10:23 ` Mark Brown
2013-11-26 10:48 ` [alsa-devel] " Padma Venkat
2013-11-26 12:20 ` Mark Brown
2013-11-27 12:38 ` Padma Venkat
2013-11-27 15:05 ` Mark Brown
2013-11-28 9:59 ` [alsa-devel] " Padma Venkat
2013-11-28 11:53 ` Mark Brown
2013-12-05 10:50 ` [alsa-devel] " Padma Venkat
2013-12-05 11:45 ` Mark Brown [this message]
2013-12-09 17:52 ` Padma Venkat
2013-12-09 17:59 ` Mark Brown
2013-11-26 5:24 ` [alsa-devel] [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Padma Venkat
2013-11-26 10:15 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2013-12-05 14:25 Mark Brown
2013-12-05 14:25 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
2013-12-06 5:14 ` [alsa-devel] " Padma Venkat
2013-12-09 17:30 ` Mark Brown
2013-12-10 16:39 ` Padma Venkat
2013-12-10 17:01 ` Mark Brown
2013-12-06 12:57 [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Mark Brown
2013-12-06 12:57 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
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=20131205114538.GO29268@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@samsung.com \
--cc=tomasz.figa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox