[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ED4EE48.8070100@metafoo.de>
Date: Tue, 29 Nov 2011 15:38:00 +0100
From: Lars-Peter Clausen <lars@...afoo.de>
To: Tomoya MORINAGA <tomoya.rohm@...il.com>
CC: Liam Girdwood <lrg@...com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
Mike Frysinger <vapier@...too.org>,
Daniel Mack <zonque@...il.com>, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, qi.wang@...el.com,
yong.y.wang@...el.com, joel.clark@...el.com, kok.howg.ewe@...el.com
Subject: Re: [PATCH v3] sound/soc/codecs: add LAPIS Semiconductor ML26124
On 11/29/2011 01:17 PM, Tomoya MORINAGA wrote:
> 2011/11/28 Lars-Peter Clausen <lars@...afoo.de>:
>
>> Also none of the inputs is> routed to the ADC, which seems a bit strange.
> This same as my referencing "wm8731.c".Could you give me more information?
>
The DAPM routes are used to do power management based on active path and for
this the routes should more or less represent the routing of internal audio
signals in your CODEC. I would expect the analog signals to go to the ADC on
the CODEC. And if you don't connect them in your DAPM routings ASoC will
probably not power-up the ADC since there are no active source signals.
Also this doesn't make much sense:
+ {"Input Mux", "Analog MIC in", "MICBIAS"},
+ {"Input Mux", "Digital MIC in", "MICBIAS"},
You have mux, but both possible settings of the mux connect to the same
source, which pretty much makes the mux useless.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists