public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] Audio capture not working with AIC23/McBSP1 on OMAP3517
Date: Wed, 26 Aug 2009 15:06:00 +0100	[thread overview]
Message-ID: <4A954148.5030602@xora.org.uk> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0309E9D83F@dbde02.ent.ti.com>

Aggarwal, Anuj wrote:
>> -----Original Message-----
>> From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
>> Sent: Wednesday, August 26, 2009 6:34 PM
>> To: Aggarwal, Anuj
>> Cc: linux-omap@vger.kernel.org; alsa-devel@alsa-project.org
>> Subject: Re: [alsa-devel] Audio capture not working with AIC23/McBSP1 on
>> OMAP3517
>>
>> 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.
>>     
> I am able to see the bit clock and frame sync coming properly.
>   
>>     
>>> Playback is working fine using the same combination.
>>>       
>>> I have tried using another instance of AIC23 codec which uses McBSP2
>>> and both playback & capture works fine there.
>>>       
>>> Has anyone faced this issue before? Any suggestions?
>>>       
>> 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.
>>     
> I am on 2.6.31-rc5. I have to check whether the new patches fix 
> anything related to this.
>   
Not having the corect pinmux settings will also cause this issue as I 
found trying to get McBSP3 working.

Graeme


  reply	other threads:[~2009-08-26 14:13 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     ` Graeme Gregory [this message]
2009-08-26 13:42   ` Jarkko Nikula
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=4A954148.5030602@xora.org.uk \
    --to=dp@xora.org.uk \
    --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