All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: arizona: Add MICVDD to mapped regulators for wm8997
Date: Mon, 28 Jul 2014 07:46:40 +0100	[thread overview]
Message-ID: <20140728064640.GA3973@lee--X1> (raw)
In-Reply-To: <1406301884-7145-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Fri, 25 Jul 2014, Charles Keepax wrote:

> The previous update adding MICVDD to the regulator mappings:
> 
> mfd: arizona: Add MICVDD to mapped regulators
> 
> Only added the mapping for wm5102 and wm5110 but wm8997 also has a
> MICVDD supply that needs to be mapped back to the main Arizona device.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/arizona-core.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index e9c3563..e0d415e 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -613,6 +613,7 @@ static const struct mfd_cell wm5110_devs[] = {
>  };
>  
>  static const char *wm8997_supplies[] = {
> +	"MICVDD",
>  	"DBVDD2",
>  	"CPVDD",
>  	"SPKVDD",

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2014-07-28  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 15:24 [PATCH 1/2] mfd: arizona: Add MICVDD to mapped regulators for wm8997 Charles Keepax
2014-07-25 15:24 ` [PATCH 2/2] mfd: arizona: Map MICVDD from extcon device to the Arizona core Charles Keepax
2014-07-28  6:47   ` Lee Jones
2014-07-28  6:46 ` Lee Jones [this message]

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=20140728064640.GA3973@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.