All of 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: Wed, 8 Jun 2011 15:22:45 +0100	[thread overview]
Message-ID: <4DEF85B5.10808@ti.com> (raw)
In-Reply-To: <307164.60382.qm@web161713.mail.bf1.yahoo.com>

On 07/06/11 20:59, hong zhang wrote:
> Liam,
> 
> Actually, I could not prove DMIC on OMAP4 blaze board is working in both kernel 2.6.35 and 2.6.38 using arecord and gstreamer-alsa.
> 
> In 2.6.35, arecord returns 44 bytes with read error
> In 2.6.38, arecord collects native data.
> 
> Gstreamer-alsa could not get voice after turning off analog captures using amixer. 
> 
> Any information regarding DMIC on OMAP4? I see people send DMIC patch to 2.6.38.
> 

DMIC works on OMAP4, can you try my branch :-

https://gitorious.org/omap-audio/linux-audio/commits/lrg/topic/omap-asoc-next-3.1

Liam

  reply	other threads:[~2011-06-08 14:22 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 [this message]
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=4DEF85B5.10808@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 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.