All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Rick Bronson <rick@efn.org>
Cc: alsa-devel@alsa-project.org, Peter Ujfalusi <peter.ujfalusi@nokia.com>
Subject: Re: WM8731 using I2S on omap3 McBSP2 issues
Date: Mon, 28 Sep 2009 08:50:32 +0300	[thread overview]
Message-ID: <20090928085032.74074fb4.jhnikula@gmail.com> (raw)
In-Reply-To: <E1MrZge-0002DY-0A@amazonia.comcast.net>

On Sat, 26 Sep 2009 08:59:52 -0700
Rick Bronson <rick@efn.org> wrote:

>   Yes, I had tried 8 before and just tried it now.  Same result.  It
> really seems like there is a DMA issue.  Can you think of anything
> else to try before I dive into the DMA code?
> 
Ok, that wasn't the reason.

Have you tried to reverse roles of codec and omap? I.e. by using
the codec as a master and omap as a slave with SND_SOC_DAIFMT_CBM_CFM.

I don't think there is any HW reason as you have seen the bit-clock and
frame sync signals toggling but I remember one case few years back
where codec had slight too high capacitive load on the bit-clock line.
That was then causing unstable frame sync as it was internally derived
directly from the bit-clock pin without any buffer. Bit-clock signal
looked just fine on oscilloscope but wasn't well enough for internal
circuits of the cpu.

So if assuming similar problem here, I could imagine that if the FSX is
used similar way directly inside the omap and if signal is not well
enough, the McBSP and DMA may not be running.

This migh be a bit far reason to look for but at least easy to try by
switching the roles as then the codec is driving the both bit-clock and
fs.


-- 
Jarkko

  reply	other threads:[~2009-09-28  5:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 15:59 WM8731 using I2S on omap3 McBSP2 issues Rick Bronson
2009-09-28  5:50 ` Jarkko Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-28 21:15 Rick Bronson
2009-09-29  8:43 ` Peter Ujfalusi
2009-09-28 16:07 Rick Bronson
2009-09-28 16:13 ` Mark Brown
2009-09-25 14:31 Rick Bronson
2009-09-26  7:56 ` Jarkko Nikula
2009-09-25 14:30 Rick Bronson
2009-09-24 17:06 Rick Bronson
2009-09-24 17:26 ` Mark Brown
2009-09-24 18:00 ` Rick Bronson
2009-09-24 18:52   ` Mark Brown
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

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=20090928085032.74074fb4.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=peter.ujfalusi@nokia.com \
    --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.