public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: twebb <taliaferro62@gmail.com>
Cc: "linux-omap@vger.kernel.org Mailing List"
	<linux-omap@vger.kernel.org>,
	alsa-devel@alsa-project.org,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Jarkko Nikula <jhnikula@gmail.com>
Subject: Re: [alsa-devel] trouble with alsa, wolfson, and TI OMAP35xx McBSP
Date: Wed, 22 Apr 2009 19:55:39 +0100	[thread overview]
Message-ID: <20090422185539.GG10356@sirena.org.uk> (raw)
In-Reply-To: <dbdb2ea60904221058w67b775f3occ07f55938fe4d03@mail.gmail.com>

On Wed, Apr 22, 2009 at 01:58:01PM -0400, twebb wrote:

> Problem 1:
> The WM8978 sample rate PLL does not seem to be stable while DCVDD =
> DBVDD = 1.8V.  FCLK mean = 44.5KHz and jittering. Increasing DCVDD and
> DBVDD voltage above 2V increases PLL stability. We have a workaround
> for this for now.

Can I suggest that you contact Wolfson's applications support team
regarding this issue - there's a web form at:

	http://www.wolfsonmicro.com/support/technical/

Looking at the datasheet the PLL is specified as requiring a minimum of
1.9V - see page 6 of:

	http://www.wolfsonmicro.com/uploads/documents/en/WM8978_Rev4.3.pdf

> Problem 2:
> Test tone is being presented by the user application, providing a 1Khz
> tone sampled at 44.1Khz. The data are S16_LE, right channel only. Left
> channel is quiet. The data seems to slip back and forth from left to
> right channel. This is reproducable and verified with a scope trace.

> Anybody have any ideas what might be going wrong here?  Traces for
> codec reg dump and mcbsp are attached.

There have been some recent threads on this list regarding the
configuration of the McBSP port configuration for various formats - it's
probably worth checking the latest changes to the OMAP code in the
topic/asoc branch of:

	git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git

That said, I2S with the CODEC as clock master is one of the most common
configurations for OMAP so I'd expect it to be well tested.  Have you
tried testing recording?

Also CCing in Peter and Jarkko, our resident OMAP audio experts.

  parent reply	other threads:[~2009-04-22 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 17:58 trouble with alsa, wolfson, and TI OMAP35xx McBSP twebb
2009-04-22 18:05 ` Menon, Nishanth
2009-04-23  6:08   ` Jarkko Nikula
2009-04-22 18:55 ` Mark Brown [this message]
2009-04-23  9:20 ` Peter Ujfalusi
2009-04-23 16:50   ` Alejandro Blanca G.
2009-04-23 18:30     ` Mark Brown
2009-04-23 18:16   ` Juha Kuikka

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=20090422185539.GG10356@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@nokia.com \
    --cc=taliaferro62@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