From: Marc Garnier <marc.garnier@heig-vd.ch>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: capturing data from the microphone
Date: Wed, 6 Jan 2010 08:58:10 +0100 [thread overview]
Message-ID: <4B444292.5070702@heig-vd.ch> (raw)
In-Reply-To: <4f3252891001051707n7e740ea5gcc217595ee354278@mail.gmail.com>
Ok, let me go into details. I work on a custom device platform based on
an Atmel at91sam9261. I wrote an alsa driver composed of 2 files
(sound/soc/atmel/myplateform_q2686.c and sound/soc/codecs/q2686.c) and I
also add this line into arch/arm/mach-at91/board-myplateform.c :
at91_add_device_ssc(AT91SAM9261_ID_SSC0, ATMEL_SSC_TX | ATMEL_SSC_RX);
When I boot my device I can see that :
Q2686 SoC Audio Codec 0.2
asoc: Q2686 <-> atmel-ssc0 mapping ok
ALSA device list:
#0: MYPLATFORM (Q2686)
And everything ok with playback :
# aplay -c 1 tone.wav
But when I want to record a pcm stream I have this error:
# arecord -v -c 1 -t wav -f S16_LE -r 8000 -d 10 input.wav
arecord: pcm_read:1629: read error: Input/output error
Any more idea?
Raymond Yau wrote:
> which device are you using ? ( pulseaudio , dmix or default device defined
> in /usr/share/alsa/cards/*.conf )
>
> post output of
>
> arecord -v -c 1 -t wav -f S16_LE -r 8000 -d 10 input.wav
>
> 2010/1/5 Marc Garnier <marc.garnier@heig-vd.ch>
>
>
>> Hi,
>>
>> I have the same kind of problem. I try to capture PCM stream thanks to
>> areacord :
>> # arecord -c 1 -t wav -f S16_LE -r 8000 -d 10 input.wav
>>
>> 30 seconds later I have the folowing message :
>> # arecord: pcm_read:1629: read error: Input/output error
>>
>> I can observe the PCM stream on an oscilloscope but no interrupt are
>> catched by the system (AIC ss0 counter remains at zero ) :
>> # cat /proc/interrupts
>> CPU0
>> 1: 275059 AIC at91_tick, rtc0, ttyS0
>> 7: 179 AIC ttyS2
>> 9: 11 AIC mmc0
>> 13: 0 AIC atmel_spi.1
>> 14: 0 AIC ssc0
>> 82: 1 GPIO alerte
>> 107: 9464 GPIO eth0
>>
>> Any idea?
>>
>>
>>
>>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2010-01-06 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 17:39 capturing data from the microphone Riccardo Magliocchetti
2010-01-05 15:24 ` Marc Garnier
2010-01-06 1:07 ` Raymond Yau
2010-01-06 7:58 ` Marc Garnier [this message]
2010-01-06 8:46 ` Raymond Yau
2010-01-06 9:09 ` Marc Garnier
2010-01-05 16:48 ` pl bossart
2010-01-05 22:12 ` Riccardo Magliocchetti
2010-01-06 23:59 ` Raymond Yau
2010-01-07 18:34 ` Riccardo Magliocchetti
2010-01-11 13:59 ` Riccardo Magliocchetti
2010-01-11 14:03 ` Jaroslav Kysela
2010-01-14 7:49 ` Raymond Yau
-- strict thread matches above, loose matches on Subject: below --
2009-12-08 14:46 How to use soc API without codec driver Marc Garnier
2009-12-08 14:51 ` Mark Brown
2009-12-09 6:39 ` Marc Garnier
2009-12-09 10:45 ` Mark Brown
[not found] ` <4B44617B.2030002@heig-vd.ch>
[not found] ` <20100106103937.GA25344@rakim.wolfsonmicro.main>
[not found] ` <4B446974.1090205@heig-vd.ch>
2010-01-06 11:39 ` capturing data from the microphone Mark Brown
2010-01-06 13:34 ` Riccardo Magliocchetti
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=4B444292.5070702@heig-vd.ch \
--to=marc.garnier@heig-vd.ch \
--cc=alsa-devel@alsa-project.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