All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Sarika <sarikababy123@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: asoc: no valid backend routes for PCM
Date: Fri, 19 Aug 2011 17:20:39 +0100	[thread overview]
Message-ID: <4E4E8D57.4000509@ti.com> (raw)
In-Reply-To: <loom.20110819T095055-703@post.gmane.org>

On 19/08/11 08:53, Sarika wrote:
> Hello,
>   I am not able to hear audio on my headset when it connect it to panda board.
> What mite be the issue?

This means you have no valid audio route from your pcm device to your headphone.

Please use the supplied UCM configuration files (with Ubuntu) to set the route or use alsamixer to do this manually.

http://www.omappedia.org/wiki/Audio_Drive_Arch

>   Also panda does not has DMIC does this make any difference ?
> 

No.

Liam

> Regards
> Sarika
> 
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2011-08-19 16:20 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
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 [this message]
     [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=4E4E8D57.4000509@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=sarikababy123@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.