All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Brian Rhodes <bgr@acdstar.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: pxa2xx-i2s
Date: Wed, 21 Jan 2009 13:23:14 +0000	[thread overview]
Message-ID: <20090121132313.GA29953@sirena.org.uk> (raw)
In-Reply-To: <49764F15.6080008@acdstar.com>

On Tue, Jan 20, 2009 at 04:24:21PM -0600, Brian Rhodes wrote:

> This method also works, and does not affect the the other stream.  The 
> difference for me really seems to be that when DREC is set and DRPL is 
> cleared when i2s is enabled it will occasionally never start.  I cannot 

Without checking the datasheet for the chip this looks broadly
reasonable to me.

> recreate the issue by with the original code if I initialize SACR1 to 
> set DREC in startup and do not reset it in hw_params.  It is possible 
> the problem is with the codec.  TLV320dac2x.

What is the clock master in your system?

> hours.  Nothing in the i2s controller documentation mentions the 
> possibility of anything in the hardware disabling replay, so I am 
> confused what is happening here.

If chip documentation were always complete and accurate the world would
be a much better place :)

  reply	other threads:[~2009-01-21 13:23 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 [this message]
     [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
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=20090121132313.GA29953@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgr@acdstar.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 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.