Re: [PATCH RESEND 1/3] mfd: arizona: Add MICVDD to mapped regulators

From: Lee Jones
Date: Mon May 19 2014 - 13:14:51 EST


> Currently, MICVDD only binds because it is both the regulator name and
> the consumer name and we will always match against the regulator name
> regardless of the consumer device. If the regulator was renamed using
> the init_data ASoC will no longer be able to locate the supply, as it
> will be looking on the CODEC device where as the MICVDD consumer is on
> the Arizona device. Add a mapping as we do for the other regulators.
>
> Signed-off-by: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> ---
> drivers/mfd/arizona-core.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)

Applied, thanks.

--
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/