From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org, Mike Frysinger <vapier@gentoo.org>,
qi.wang@intel.com, Takashi Iwai <tiwai@suse.de>,
Tomoya MORINAGA <tomoya.rohm@gmail.com>,
linux-kernel@vger.kernel.org, yong.y.wang@intel.com,
kok.howg.ewe@intel.com, Daniel Mack <zonque@gmail.com>,
Liam Girdwood <lrg@ti.com>,
joel.clark@intel.com
Subject: Re: [PATCH v3] sound/soc/codecs: add LAPIS Semiconductor ML26124
Date: Tue, 29 Nov 2011 14:38:43 +0000 [thread overview]
Message-ID: <20111129143842.GC26800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED4EE48.8070100@metafoo.de>
On Tue, Nov 29, 2011 at 03:38:00PM +0100, Lars-Peter Clausen wrote:
> 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.
Plus the fact that the MICBIAS is unlikely to be directly connected to
either input within the CODEC, it will almost certainly be connected by
circuitry on the board and therefore mapped by the machine driver for
the system.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Tomoya MORINAGA <tomoya.rohm@gmail.com>,
Liam Girdwood <lrg@ti.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Mike Frysinger <vapier@gentoo.org>,
Daniel Mack <zonque@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
qi.wang@intel.com, yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com
Subject: Re: [PATCH v3] sound/soc/codecs: add LAPIS Semiconductor ML26124
Date: Tue, 29 Nov 2011 14:38:43 +0000 [thread overview]
Message-ID: <20111129143842.GC26800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED4EE48.8070100@metafoo.de>
On Tue, Nov 29, 2011 at 03:38:00PM +0100, Lars-Peter Clausen wrote:
> 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.
Plus the fact that the MICBIAS is unlikely to be directly connected to
either input within the CODEC, it will almost certainly be connected by
circuitry on the board and therefore mapped by the machine driver for
the system.
next prev parent reply other threads:[~2011-11-29 14:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 10:05 [PATCH v3] sound/soc/codecs: add LAPIS Semiconductor ML26124 Tomoya MORINAGA
2011-11-28 12:21 ` Lars-Peter Clausen
2011-11-28 12:21 ` Lars-Peter Clausen
2011-11-29 12:17 ` Tomoya MORINAGA
2011-11-29 14:38 ` Lars-Peter Clausen
2011-11-29 14:38 ` Lars-Peter Clausen
2011-11-29 14:38 ` Mark Brown [this message]
2011-11-29 14:38 ` Mark Brown
2011-12-01 7:46 ` Tomoya MORINAGA
2011-12-01 19:36 ` Lars-Peter Clausen
2011-12-01 19:36 ` Lars-Peter Clausen
2011-12-02 5:12 ` Tomoya MORINAGA
2011-11-28 13:23 ` Mark Brown
2011-11-29 12:14 ` Tomoya MORINAGA
2011-11-29 12:29 ` Mark Brown
2011-11-29 12:29 ` Mark Brown
2011-12-01 7:34 ` Tomoya MORINAGA
2011-12-01 7:40 ` Takashi Iwai
2011-12-01 7:40 ` Takashi Iwai
2011-12-01 7:57 ` Tomoya MORINAGA
2011-12-01 7:57 ` Tomoya MORINAGA
2011-12-01 11:11 ` Mark Brown
2011-12-01 11:11 ` Mark Brown
2011-12-02 0:33 ` Tomoya MORINAGA
2011-12-02 1:06 ` Mark Brown
2011-12-02 1:06 ` Mark Brown
2011-12-02 2:20 ` Tomoya MORINAGA
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=20111129143842.GC26800@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=qi.wang@intel.com \
--cc=tiwai@suse.de \
--cc=tomoya.rohm@gmail.com \
--cc=vapier@gentoo.org \
--cc=yong.y.wang@intel.com \
--cc=zonque@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.