From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rick Bronson <rick@efn.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: WM8731 using I2S on omap3 McBSP2 issues
Date: Thu, 24 Sep 2009 19:52:46 +0100 [thread overview]
Message-ID: <20090924185246.GA25783@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <E1Mqsce-0002nt-OD@amazonia.comcast.net>
On Thu, Sep 24, 2009 at 11:00:52AM -0700, Rick Bronson wrote:
> Mark,
> > This suggests that the DMA isn't happening which usually means that the
> > CPU isn't seeing all the clocks it's supposed to. I'm not familiar
> > enough with the OMAP internals to know if you've set the CPU up
> > properly.
> I've poured over the relavent code for this and am pretty sure I
> don't need to touch it. The same code works on the beagleboard, at
> least the DMA part. But you never know...
You shouldn't need to touch the DMA code itself, it's normally an issue
with the clocks and/or the pinmux code not managing to get the signals
required to clock the data transfer.
> BTW, when I do a aplay, the trace looks the same except ACDDAT is
> low.
Yes, that's what I'd expect - this was just an attempt to confirm that
the CODEC is happy.
next prev parent reply other threads:[~2009-09-24 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 17:06 WM8731 using I2S on omap3 McBSP2 issues Rick Bronson
2009-09-24 17:26 ` Mark Brown
2009-09-24 18:00 ` Rick Bronson
2009-09-24 18:52 ` Mark Brown [this message]
2009-09-24 22:37 ` Rick Bronson
2009-09-25 5:53 ` Mark Brown
2009-09-25 6:03 ` Peter Ujfalusi
2009-09-25 9:12 ` Peter Ujfalusi
-- strict thread matches above, loose matches on Subject: below --
2009-09-25 14:30 Rick Bronson
2009-09-25 14:31 Rick Bronson
2009-09-26 7:56 ` Jarkko Nikula
2009-09-26 15:59 Rick Bronson
2009-09-28 5:50 ` Jarkko Nikula
2009-09-28 16:07 Rick Bronson
2009-09-28 16:13 ` Mark Brown
2009-09-28 21:15 Rick Bronson
2009-09-29 8:43 ` Peter Ujfalusi
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=20090924185246.GA25783@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=rick@efn.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.