All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Rhodes <bgr@acdstar.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: pxa2xx-i2s
Date: Fri, 23 Jan 2009 10:50:39 -0600	[thread overview]
Message-ID: <4979F55F.70600@acdstar.com> (raw)
In-Reply-To: <20090121222718.GA23539@sirena.org.uk>

Mark Brown wrote:
> On Wed, Jan 21, 2009 at 02:13:12PM -0600, Brian Rhodes wrote:
>
>   
>> No, the 270 is the clock master on the I2S bus.  The codec is sourcing 
>> the clock input using the PLL.  I apologize for being unclear.
>>     
>
> I think it's me that's not being clear, sorry - I'm trying to find out
> is if the LRCLK and BCLK signals on the I2S bus itself are being driven
> by the codec or by the I2S controller.  If the codec driver is the clock
> master then your earlier speculation that your problems with the I2S
> controller may be due to some interaction with the codec driver are more
> likely to be true.
>
>   
I'm curious if you think this problem may be arising from the toggling 
of the direction of BCLK on the PXA while the I2S clock is enabled.  I'm 
sure there are people who have a reason for switching the bit clock 
master, but I'm thinking that this should not be explicitly done if it 
is not changing.

  parent reply	other threads:[~2009-01-23 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 14:31 ASoC: pxa2xx-i2s Brian Rhodes
2009-01-20 15:44 ` Karl Beldan
2009-01-20 17:04   ` Brian Rhodes
2009-01-20 22:24     ` Brian Rhodes
2009-01-21 13:23       ` Mark Brown
     [not found]         ` <49775159.7070708@linespeed.net>
2009-01-21 19:32           ` Mark Brown
2009-01-21 20:13             ` Brian Rhodes
2009-01-21 22:27               ` Mark Brown
2009-01-22 17:03                 ` Brian Rhodes
2009-01-23 16:50                 ` Brian Rhodes [this message]
2009-01-23 16:58                   ` Mark Brown
2009-05-08 22:13                   ` Karl Beldan

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=4979F55F.70600@acdstar.com \
    --to=bgr@acdstar.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    /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.