From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
broonie@kernel.org, lgirdwood@gmail.com, sameo@linux.intel.com
Subject: Re: [PATCH 1/3 v4] mfd: arizona: Export function to control subsystem DVFS
Date: Wed, 9 Jul 2014 15:08:01 +0100 [thread overview]
Message-ID: <20140709140801.GA2635@lee--X1> (raw)
In-Reply-To: <1404313973-1030-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Wed, 02 Jul 2014, Charles Keepax wrote:
> From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
>
> Moving this control from being a side-effect of the LDO1
> regulator driver to a specific exported function.
>
> Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-core.c | 89 ++++++++++++++++++++++++++++++++++++++
> include/linux/mfd/arizona/core.h | 12 +++++
> 2 files changed, 101 insertions(+), 0 deletions(-)
Patch looks okay to me now. Is it okay to apply it on its own?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-07-09 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:12 [PATCH 0/3 v4] arizona: Improvements to codec DVFS control Charles Keepax
2014-07-02 15:12 ` [PATCH 1/3 v4] mfd: arizona: Export function to control subsystem DVFS Charles Keepax
2014-07-09 14:08 ` Lee Jones [this message]
2014-07-09 14:46 ` Charles Keepax
2014-07-25 13:05 ` Charles Keepax
2014-07-25 14:17 ` Lee Jones
2014-07-02 15:12 ` [PATCH 2/3 v4] ASoC: wm_adsp: Move DVFS control into codec driver Charles Keepax
2014-07-02 15:12 ` [PATCH 3/3 v4] ASoC: arizona: Add DVFS handling for sample rate control Charles Keepax
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=20140709140801.GA2635@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=patches@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