From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: rf@opensource.wolfsonmicro.com, lee.jones@linaro.org,
sameo@linux.intel.com, lgirdwood@gmail.com,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3 v4 RESEND] ASoC: arizona: Add DVFS handling for sample rate control
Date: Tue, 12 Aug 2014 14:34:58 +0100 [thread overview]
Message-ID: <20140812133458.GD15833@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140808133510.GC2665@opensource.wolfsonmicro.com>
On Fri, Aug 08, 2014 at 02:35:10PM +0100, Richard Fitzgerald wrote:
> From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
>
> Some codecs need to boost DVFS for higher sample rates.
>
> Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
Hi Mark,
Would it be possible to get an Ack for the ASoC patches here, Lee
said it would be ok to put the series through the MFD tree once
we have an ack? Unless you have any issues with the series?
Thanks,
Charles
next prev parent reply other threads:[~2014-08-12 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:32 [PATCH 1/3 v4 RESEND] mfd: arizona: Export function to control subsystem DVFS Richard Fitzgerald
2014-08-08 13:34 ` [PATCH 2/3 v4 RESEND] ASoC: wm_adsp: Move DVFS control into codec driver Richard Fitzgerald
2014-08-08 13:35 ` [PATCH 3/3 v4 RESEND] ASoC: arizona: Add DVFS handling for sample rate control Richard Fitzgerald
2014-08-12 13:34 ` Charles Keepax [this message]
2014-08-12 15:57 ` Mark Brown
2014-08-21 10:40 ` [PATCH 1/3 v4 RESEND] mfd: arizona: Export function to control subsystem DVFS Lee Jones
2014-08-25 10:15 ` Richard Fitzgerald
2014-09-01 14:47 ` Richard Fitzgerald
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=20140812133458.GD15833@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox