public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Audio capture not working with AIC23/McBSP1 on OMAP3517
Date: Wed, 26 Aug 2009 16:42:39 +0300	[thread overview]
Message-ID: <20090826164239.a574d4ab.jhnikula@gmail.com> (raw)
In-Reply-To: <20090826130356.GB29299@sirena.org.uk>

On Wed, 26 Aug 2009 14:03:56 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> On Wed, Aug 26, 2009 at 06:30:52PM +0530, Aggarwal, Anuj wrote:
> 
> > I am trying to capture audio through LineIn on my OMAP3517 EVM, using 
> > AIC23 codec and McBSP1, and getting the following error:
> 
> > arecord: pcm_read:1529: read error: Input/output error
> 
> That suggests that DMA isn't happening - might be worth checking to see
> that clocks are being generated properly.
> 
> > Playback is working fine using the same combination. 
> 
What is exactly your configuration: Is the AIC23 master or slave, how
is the McBSP1 is connected (it has additional FSR and CLKR pins
compared to other ports) and is the pin muxing correct?

I think I have tested the McBSP1 on Beagle but definitely only OMAP as a
master since my codec was oscilloscope.

> Which kernel are you using?  There are rather a lot of McBSP changes
> queued up for 2.6.32.  If this ever worked in the past a git bisect
> might be interesting.

Those recent patches should not any effect into this since they are
mostly playing with the McBSP and DMA interfacing. What comes to my
mind if muxing is correct and if codec is master, this might be related
to those McBSP1 FSR and CLKR setup.


-- 
Jarkko

  parent reply	other threads:[~2009-08-26 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 13:00 Audio capture not working with AIC23/McBSP1 on OMAP3517 Aggarwal, Anuj
2009-08-26 13:03 ` [alsa-devel] " Mark Brown
2009-08-26 13:19   ` Aggarwal, Anuj
2009-08-26 14:06     ` [alsa-devel] " Graeme Gregory
2009-08-26 13:42   ` Jarkko Nikula [this message]
2009-08-26 15:01     ` Jarkko Nikula
2009-08-27  9:37       ` Aggarwal, Anuj
2009-08-27 11:12         ` Jarkko Nikula
2009-08-28  6:55           ` Peter Ujfalusi
2009-08-28 10:51             ` Jarkko Nikula
2009-08-28 12:05               ` [alsa-devel] " Mark Brown

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=20090826164239.a574d4ab.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox