From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"perex@perex.cz" <perex@perex.cz>,
Stephen Warren <swarren@nvidia.com>, "lrg@ti.com" <lrg@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] ASoC: tegra: use dmaengine based dma driver
Date: Mon, 2 Jul 2012 17:47:18 +0100 [thread overview]
Message-ID: <20120702164717.GH25093@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FF1D00D.6040402@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
On Mon, Jul 02, 2012 at 10:45:01AM -0600, Stephen Warren wrote:
> to work. No audio is heard, and aplay eventually exits with the
> following error message:
For values of eventually that will be about 10s by default.
> aplay: pcm_write:1603: write error: Input/output error
> I believe this means that the DMA simply isn't operating.
Yes, normally.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-02 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:34 [PATCH] ARM: tegra: apbio: use dmaengine based dma driver Laxman Dewangan
2012-06-29 11:34 ` [PATCH] ASoC: tegra: " Laxman Dewangan
2012-06-29 17:02 ` Stephen Warren
2012-06-30 15:08 ` Laxman Dewangan
2012-07-02 8:25 ` Laxman Dewangan
2012-07-02 16:45 ` Stephen Warren
2012-07-02 16:47 ` Mark Brown [this message]
2012-07-03 6:26 ` Laxman Dewangan
2012-07-18 8:59 ` Laxman Dewangan
2012-07-02 16:46 ` Stephen Warren
2012-07-03 6:29 ` Laxman Dewangan
2012-07-03 10:09 ` Mark Brown
2012-07-03 19:07 ` 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=20120702164717.GH25093@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).