From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stuart Longland <redhatter@gentoo.org>
Cc: alsa-devel@alsa-project.org, gnutoo <GNUtoo@no-log.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ASoC: Hooking a TI CODEC to a i.MX27 MCU
Date: Thu, 27 May 2010 01:47:03 +0100 [thread overview]
Message-ID: <20100527004702.GA22091@sirena.org.uk> (raw)
In-Reply-To: <20100526132129.GA13644@www.longlandclan.yi.org>
On Wed, May 26, 2010 at 11:21:36PM +1000, Stuart Longland wrote:
> At the moment, when I go to play audio; I see the CODEC being set up ...
> but despite the clocks being present -- I see no audio data, and the DMA
> transfer eventually times out with the message "playback write error
> (DMA or IRQ trouble?)" after 10 seconds. Would anyone know where I'd
> look for that? Is there something else needed in the configuration of
> the SSI driver for this to work?
This most likely means your CPU side configuration is broken and clocks
aren't being routed through. Try looking at the AUDMUX debugfs files to
verify your configuration, and also try routing out to another external
SSI port so you can probe signals. Make sure the relevant pins on the
i.MX are configured into the appropriate mode for use by the i.MX too.
Note also that the current driver only supports CODEC as clock master.
next prev parent reply other threads:[~2010-05-27 0:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 7:49 ASoC: Hooking a TI CODEC to a i.MX27 MCU Stuart Longland
2010-05-24 10:49 ` Liam Girdwood
2010-05-25 0:41 ` Stuart Longland
2010-05-25 2:26 ` Stuart Longland
2010-05-25 3:26 ` Stuart Longland
2010-05-25 16:46 ` gnutoo
2010-05-26 13:21 ` Stuart Longland
2010-05-27 0:47 ` Mark Brown [this message]
2010-05-28 2:06 ` Stuart Longland
2010-05-28 5:55 ` Eric Bénard
2010-05-28 11:08 ` Mark Brown
2010-05-28 13:10 ` Eric Bénard
2010-06-01 3:30 ` Stuart Longland
2010-06-01 5:07 ` Stuart Longland
2010-06-01 11:32 ` Stuart Longland
2010-06-03 11:14 ` Mark Brown
2010-06-03 11:43 ` Stuart Longland
2010-06-03 11:57 ` Mark Brown
2010-05-28 12:27 ` Mark Brown
2010-05-29 8:59 ` Stuart Longland
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=20100527004702.GA22091@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=GNUtoo@no-log.org \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=redhatter@gentoo.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.