Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: hong zhang <henryzhang62@yahoo.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: asoc: no valid backend routes for PCM: SDP4430 Media
Date: Tue, 7 Jun 2011 09:38:35 +0100	[thread overview]
Message-ID: <4DEDE38B.2040408@ti.com> (raw)
In-Reply-To: <76445.36914.qm@web161713.mail.bf1.yahoo.com>

On 07/06/11 01:13, hong zhang wrote:
> List,
> 
> After capturing data from DMIC on OMAP4 blaze board with kernel 2.6.38 and save wav data to 38.wav.
> 
> But aplay complains "no valid backend routes". See following,
> 
> $aplay -f dat 38.wav 
> [  157.167724] asoc: no valid backend routes for PCM: SDP4430 Media
> aplay: main:654: audio open error: Invalid argument
> 

This means you have not configured an audio route for playback (i.e. the audio is not routed anywhere from pcm hw:0,0). Use alsamixer and configure the kcontrols to define the audio path. The kcontrol mappings to audio paths are detailed here for OMAP4 :-

http://omappedia.org/wiki/Audio_Drive_Arch

Liam

  reply	other threads:[~2011-06-07  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  0:13 asoc: no valid backend routes for PCM: SDP4430 Media hong zhang
2011-06-07  8:38 ` Liam Girdwood [this message]
2011-06-07 19:59   ` hong zhang
2011-06-08 14:22     ` Liam Girdwood
2011-06-08 19:08       ` hong zhang
2011-06-09  9:42         ` Liam Girdwood
2011-06-09 17:45           ` hong zhang
2011-06-09 17:48             ` Liam Girdwood
2011-06-09 17:52               ` hong zhang
2011-08-19  7:53                 ` asoc: no valid backend routes for PCM Sarika
2011-08-19 16:20                   ` Liam Girdwood
     [not found]                     ` <CAHgabbYxe-mzwhxiivj5Xmqdq3FQuZ3ZFhgU4wy_bCosm2BhwA@mail.gmail.com>
2011-08-22 10:54                       ` Liam Girdwood

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=4DEDE38B.2040408@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=henryzhang62@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox