From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 3/3] ASoC: codecs: add driver for max9768 amplifier
Date: Mon, 30 Jan 2012 21:54:09 +0000 [thread overview]
Message-ID: <20120130215409.GA16187@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327677023-29310-3-git-send-email-w.sang@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 408 bytes --]
On Fri, Jan 27, 2012 at 04:10:23PM +0100, Wolfram Sang wrote:
> Add a driver supporting the volume control and the mute pin. Shdn pin
> and DAPM are not taken care of yet.
Given your comments about being out of time I went ahead and applied
this, I'll do a patch fixing up the main review comments I had on top of
it (the Mute Switch name and the always_false thing which you now fixed
in the regmap core).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>, Liam Girdwood <lrg@ti.com>
Subject: Re: [alsa-devel] [PATCH 3/3] ASoC: codecs: add driver for max9768 amplifier
Date: Mon, 30 Jan 2012 21:54:09 +0000 [thread overview]
Message-ID: <20120130215409.GA16187@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327677023-29310-3-git-send-email-w.sang@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
On Fri, Jan 27, 2012 at 04:10:23PM +0100, Wolfram Sang wrote:
> Add a driver supporting the volume control and the mute pin. Shdn pin
> and DAPM are not taken care of yet.
Given your comments about being out of time I went ahead and applied
this, I'll do a patch fixing up the main review comments I had on top of
it (the Mute Switch name and the always_false thing which you now fixed
in the regmap core).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-30 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 15:10 [PATCH 1/3] regmap: Properly round reg_bytes and val_bytes Wolfram Sang
2012-01-27 15:10 ` Wolfram Sang
2012-01-27 15:10 ` [PATCH 2/3] regmap: Add support for 2/6 register formating Wolfram Sang
2012-01-27 15:10 ` Wolfram Sang
2012-01-27 16:28 ` Mark Brown
2012-01-27 16:28 ` Mark Brown
2012-01-27 15:10 ` [PATCH 3/3] ASoC: codecs: add driver for max9768 amplifier Wolfram Sang
2012-01-27 15:10 ` Wolfram Sang
2012-01-27 16:25 ` Mark Brown
2012-01-27 16:25 ` Mark Brown
2012-01-30 21:54 ` Mark Brown [this message]
2012-01-30 21:54 ` [alsa-devel] " Mark Brown
2012-01-27 16:28 ` [PATCH 1/3] regmap: Properly round reg_bytes and val_bytes Mark Brown
2012-01-27 16:28 ` Mark Brown
2012-01-28 1:14 ` Wolfram Sang
2012-01-28 1:14 ` Wolfram Sang
2012-01-30 13:21 ` Mark Brown
2012-01-30 13:21 ` Mark Brown
2012-01-30 13:35 ` Wolfram Sang
2012-01-30 13:35 ` Wolfram Sang
2012-01-30 13:45 ` Mark Brown
2012-01-30 13:45 ` Mark Brown
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=20120130215409.GA16187@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=w.sang@pengutronix.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 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.