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 RESEND 1/3] mfd: arizona: Add MICVDD to mapped regulators
Date: Mon, 19 May 2014 18:14:42 +0100 [thread overview]
Message-ID: <20140519171442.GA20435@lee--X1> (raw)
In-Reply-To: <1400517329-1103-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
> 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@opensource.wolfsonmicro.com>
> ---
> 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
prev parent reply other threads:[~2014-05-19 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 16:35 [PATCH RESEND 1/3] mfd: arizona: Add MICVDD to mapped regulators Charles Keepax
2014-05-19 16:35 ` [PATCH RESEND 2/3] mfd: wm8997: Add registers for high power mode Charles Keepax
2014-05-19 17:15 ` Lee Jones
2014-05-19 16:35 ` [PATCH RESEND 3/3] mfd: arizona: Correct error message for addition of main IRQ chip Charles Keepax
2014-05-19 17:15 ` Lee Jones
2014-05-19 17:14 ` 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=20140519171442.GA20435@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