linux-kernel - Re: [PATCH 1/2] mfd: arizona: Add MICVDD to mapped regulators for wm8997

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140728064640.GA3973@lee--X1>
Date:	Mon, 28 Jul 2014 07:46:40 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	sameo@...ux.intel.com, patches@...nsource.wolfsonmicro.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mfd: arizona: Add MICVDD to mapped regulators for
 wm8997

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@...nsource.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/