mirror of https://lore.kernel.org/lkml/
 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 2/2] mfd: arizona: Map MICVDD from extcon device to the Arizona core
Date: Mon, 28 Jul 2014 07:47:10 +0100	[thread overview]
Message-ID: <20140728064710.GB3973@lee--X1> (raw)
In-Reply-To: <1406301884-7145-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Fri, 25 Jul 2014, Charles Keepax wrote:

> The extcon driver should be able to get its regulator against rather
> than against the main arizona device, we must add a supply mapping
> allowing the regulator to be located. This patch does so.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/arizona-core.c |   20 ++++++++++++++++----
>  1 files changed, 16 insertions(+), 4 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> index e0d415e..cf3689f 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -578,17 +578,21 @@ static const struct mfd_cell early_devs[] = {
>  };
>  
>  static const char *wm5102_supplies[] = {
> +	"MICVDD",
>  	"DBVDD2",
>  	"DBVDD3",
>  	"CPVDD",
>  	"SPKVDDL",
>  	"SPKVDDR",
> -	"MICVDD",
>  };
>  
>  static const struct mfd_cell wm5102_devs[] = {
>  	{ .name = "arizona-micsupp" },
> -	{ .name = "arizona-extcon" },
> +	{
> +		.name = "arizona-extcon",
> +		.parent_supplies = wm5102_supplies,
> +		.num_parent_supplies = 1, /* We only need MICVDD */
> +	},
>  	{ .name = "arizona-gpio" },
>  	{ .name = "arizona-haptics" },
>  	{ .name = "arizona-pwm" },
> @@ -601,7 +605,11 @@ static const struct mfd_cell wm5102_devs[] = {
>  
>  static const struct mfd_cell wm5110_devs[] = {
>  	{ .name = "arizona-micsupp" },
> -	{ .name = "arizona-extcon" },
> +	{
> +		.name = "arizona-extcon",
> +		.parent_supplies = wm5102_supplies,
> +		.num_parent_supplies = 1, /* We only need MICVDD */
> +	},
>  	{ .name = "arizona-gpio" },
>  	{ .name = "arizona-haptics" },
>  	{ .name = "arizona-pwm" },
> @@ -621,7 +629,11 @@ static const char *wm8997_supplies[] = {
>  
>  static const struct mfd_cell wm8997_devs[] = {
>  	{ .name = "arizona-micsupp" },
> -	{ .name = "arizona-extcon" },
> +	{
> +		.name = "arizona-extcon",
> +		.parent_supplies = wm8997_supplies,
> +		.num_parent_supplies = 1, /* We only need MICVDD */
> +	},
>  	{ .name = "arizona-gpio" },
>  	{ .name = "arizona-haptics" },
>  	{ .name = "arizona-pwm" },

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

  reply	other threads:[~2014-07-28  6:47 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 [this message]
2014-07-28  6:46 ` [PATCH 1/2] mfd: arizona: Add MICVDD to mapped regulators for wm8997 Lee Jones

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=20140728064710.GB3973@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®