alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"dp@opensource.wolfsonmicro.com" <dp@opensource.wolfsonmicro.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 10/11] ASoC: tegra: Harmony machine support
Date: Tue, 4 Jan 2011 15:30:20 +0000	[thread overview]
Message-ID: <20110104153020.GE24774@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF030FD79220@HQMAIL01.nvidia.com>

On Mon, Jan 03, 2011 at 11:39:32AM -0800, Stephen Warren wrote:
> Mark Brown wrote:

> > It might be interesting to try having the CODEC master the I2S bus - it
> > might not change anything, but it sometimes shows up if one of the clock
> > lines is misconfigured.

> Having the codec be master of the bit and frame clocks appears to completely
> solve the noise issues. I do notice that different sample rates play the same
> audio at different pitches though, so something is still wrong, but it's most
> likely to be incorrect codec MCLK input right now; I'll keep investigating...

That's progress; with the CODEC as master all the clocks within the
CODEC will be configured correctly in relation to one another which will
help with the noise - probably the MCLK rate does have issues like you
say, with the CODEC as master pitch variations are a likely symptom.

      reply	other threads:[~2011-01-04 15:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1292622090-21896-1-git-send-email-swarren@nvidia.com>
     [not found] ` <1292622090-21896-8-git-send-email-swarren@nvidia.com>
     [not found]   ` <20101217220029.GD25609@sirena.org.uk>
2010-12-22 18:30     ` [PATCH 07/11] ASoC: tegra: Add tegra-das driver Stephen Warren
2010-12-22 20:11       ` Mark Brown
2011-01-05 22:58         ` Stephen Warren
2011-01-05 23:18           ` Mark Brown
2011-01-05 23:27             ` Stephen Warren
2011-01-05 23:33               ` Mark Brown
2011-01-06  0:20                 ` Stephen Warren
2011-01-06  0:59                   ` Mark Brown
2011-01-06 17:46                     ` Stephen Warren
2011-01-06 21:02                       ` Mark Brown
2011-01-06 21:58                         ` Stephen Warren
2011-01-06 22:13                           ` Mark Brown
     [not found] ` <1292622090-21896-9-git-send-email-swarren@nvidia.com>
     [not found]   ` <20101217220658.GG25609@sirena.org.uk>
2010-12-22 19:03     ` [PATCH 08/11] ASoC: tegra: Add tegra-pcm driver Stephen Warren
2010-12-22 20:16       ` Mark Brown
     [not found] ` <1292622090-21896-11-git-send-email-swarren@nvidia.com>
     [not found]   ` <20101217222636.GJ25609@sirena.org.uk>
     [not found]     ` <74CDBE0F657A3D45AFBB94109FB122FF030FD7885D@HQMAIL01.nvidia.com>
     [not found]       ` <20101217230618.GA28364@sirena.org.uk>
     [not found]         ` <20101220211131.GG14986@sirena.org.uk>
2010-12-23  1:13           ` [PATCH 10/11] ASoC: tegra: Harmony machine support Stephen Warren
2010-12-23  2:19             ` Mark Brown
2011-01-03 19:39               ` Stephen Warren
2011-01-04 15:30                 ` Mark Brown [this message]

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=20110104153020.GE24774@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.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;
as well as URLs for NNTP newsgroup(s).