From: Christophe Aeschlimann <c.aeschlimann-5/WUhD8XThOVQ4qyx6sgCw@public.gmane.org>
To: "Rajashekhara, Sudhakar" <sudhakar.raj-l0cyMroinI0@public.gmane.org>
Cc: "khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org"
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
"alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org"
<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
"davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org"
<davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: ALSA issue on DA850/OMAP-L138/AM18x
Date: Wed, 16 Feb 2011 15:07:57 +0100 [thread overview]
Message-ID: <4D5BDA3D.5080905@acn-group.ch> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59302484734E0-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
Hi Sudhakar,
On 18.01.2011 05:43, Rajashekhara, Sudhakar wrote:
[...]
> With the above fixes, arecord and aplay does not work for the first time.
> Couple of times I get the below error:
>
> root@da850-omapl138-evm:~# arecord -f dat | aplay -f dat
> arecord: main:608: audio open error: Invalid argument
> aplay: playback:2297: read error
> root@da850-omapl138-evm:~# arecord -f dat | aplay -f dat
> aplay: main:608: audio open error: Invalid argument
> Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz,
Stereo
>
> Third time arecord and aplay work normally.
>
> Has anyone seen such issues on DA850 or any other platform?
>
> I am currently debugging this issue. I'll submit the above patch to
community
> once the issue of fixed.
I'm facing the same issue here.
Did you make any progress on that one ?
> Regards,
> Sudhakar
Regards,
Christophe
next prev parent reply other threads:[~2011-02-16 14:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 4:43 ALSA issue on DA850/OMAP-L138/AM18x Rajashekhara, Sudhakar
2011-01-18 18:04 ` Kevin Hilman
2011-01-18 19:16 ` Mark Brown
[not found] ` <B85A65D85D7EB246BE421B3FB0FBB59302484734E0-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2011-01-18 19:02 ` Dan Sharon
2011-01-20 5:05 ` Rajashekhara, Sudhakar
[not found] ` <B85A65D85D7EB246BE421B3FB0FBB593024850919E-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2011-01-20 15:33 ` Dan Sharon
2011-01-19 1:09 ` Nori, Sekhar
2011-02-16 14:07 ` Christophe Aeschlimann [this message]
2011-02-17 4:23 ` Rajashekhara, Sudhakar
2011-03-07 8:40 ` Christophe Aeschlimann
2011-03-08 4:40 ` Rajashekhara, Sudhakar
2011-03-08 13:32 ` Christophe Aeschlimann
[not found] ` <4D762FEB.3010003-5/WUhD8XThOVQ4qyx6sgCw@public.gmane.org>
2011-03-21 8:20 ` Christophe Aeschlimann
2011-03-21 11:24 ` Bedia, Vaibhav
[not found] ` <FCCFB4CDC6E5564B9182F639FC3560870370B2BA32-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2011-03-21 12:15 ` Christophe Aeschlimann
2011-03-21 13:11 ` Bedia, Vaibhav
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=4D5BDA3D.5080905@acn-group.ch \
--to=c.aeschlimann-5/wuhd8xthovq4qyx6sgcw@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=sudhakar.raj-l0cyMroinI0@public.gmane.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;
as well as URLs for NNTP newsgroup(s).