From: Mark Brown <broonie@kernel.org>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Sachin Kamat <sachin.kamat@linaro.org>,
Ralph Birt <ralph.birt@maximintegrated.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Jerry Wong <jerry.wong@maximintegrated.com>,
Evan Ragsdale <evan.ragsdale@maximintegrated.com>,
Dylan Reid <dgreid@chromium.org>,
linux-kernel@vger.kernel.org,
Matthew Mowdy <Matthew.Mowdy@maximintegrated.com>
Subject: Re: [PATCH v2] ASoC: max98090: add digital mic mux to record path
Date: Fri, 17 May 2013 12:07:33 +0100 [thread overview]
Message-ID: <20130517110733.GK1627@sirena.org.uk> (raw)
In-Reply-To: <1368731034-30135-1-git-send-email-abrestic@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
On Thu, May 16, 2013 at 12:03:54PM -0700, Andrew Bresticker wrote:
> The max98090 driver currently treats the digital mic enable as a supply
> on the record path, causing the digital mic enable to always be turned on
> when attempting to record. This is incorrect, however, since the digital
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-17 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 17:48 [PATCH] " Andrew Bresticker
[not found] ` <A453F1AE3B5DC14DB19666C506CE75A710ABEB1EFF@ITSVLEX06.it.maxim-ic.internal>
[not found] ` <9F78FA13B8C7A749B307D9AECB279EB713E7B327F3@ITSVLEX06.it.maxim-ic.internal>
2013-05-16 6:43 ` Andrew Bresticker
2013-05-16 17:43 ` Mark Brown
2013-05-16 17:52 ` Mark Brown
2013-05-16 19:03 ` [PATCH v2] " Andrew Bresticker
2013-05-17 11:07 ` Mark Brown [this message]
2013-05-16 19:15 ` [PATCH] " Matthew Mowdy
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=20130517110733.GK1627@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Matthew.Mowdy@maximintegrated.com \
--cc=abrestic@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@chromium.org \
--cc=evan.ragsdale@maximintegrated.com \
--cc=jerry.wong@maximintegrated.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=ralph.birt@maximintegrated.com \
--cc=sachin.kamat@linaro.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®