From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, linux-input@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere
Date: Fri, 30 Nov 2012 11:09:39 +0100 [thread overview]
Message-ID: <20121130100939.GC3176@sortiz-mobl> (raw)
In-Reply-To: <1354020025-23881-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Tue, Nov 27, 2012 at 12:40:22PM +0000, Mark Brown wrote:
> Some other device functions need to integrate with signal sources in the
> audio portion (primarily for haptics) so allow CODEC to export the DAPM
> context by pointing to it from the core driver.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> include/linux/mfd/arizona/core.h | 4 ++++
> 1 file changed, 4 insertions(+)
Probably too late, but I think it would make sense to merge this one through
your asoc tree:
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-11-30 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:40 [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Mark Brown
2012-11-27 12:40 ` [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs Mark Brown
2012-11-27 19:56 ` Dmitry Torokhov
2012-11-27 20:00 ` Mark Brown
2012-11-28 7:11 ` Dmitry Torokhov
2012-11-28 13:49 ` Mark Brown
2012-11-27 12:40 ` [PATCH 3/4] ASoC: wm5102: Implement haptics support Mark Brown
2012-11-27 12:40 ` [PATCH 4/4] ASoC: wm5110: " Mark Brown
2012-11-30 10:09 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-27 10:33 [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Mark Brown
2012-11-27 7:08 Mark Brown
2012-11-26 21:39 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=20121130100939.GC3176@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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.