From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2 RESEND] mfd: arizona: Update DT binding to support MICVDD init_data
Date: Fri, 11 Jul 2014 09:32:27 +0100 [thread overview]
Message-ID: <20140711083227.GL11948@lee--X1> (raw)
In-Reply-To: <1405008249-4370-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Thu, 10 Jul 2014, Charles Keepax wrote:
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> index fd51988..5c7e723 100644
> --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> @@ -42,13 +42,15 @@ Optional properties:
> the chip default will be used. If present exactly five values must
> be specified.
>
> - - DCVDD-supply : Power supply, only needs to be specified if DCVDD is being
> - externally supplied. As covered in
Patch 1 in this series just added these two lines. Normally I'd ask
you to squash them, but as they've been around for a while already and
_might_ have (benefit of the doubt) originated from separate
patch-sets, I'll apply it anyway.
Applied, thanks.
> + - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if
> + they are being externally supplied. As covered in
> Documentation/devicetree/bindings/regulator/regulator.txt
>
> Optional subnodes:
> - ldo1 : Initial data for the LDO1 regulator, as covered in
> Documentation/devicetree/bindings/regulator/regulator.txt
> + - micvdd : Initial data for the MICVDD regulator, as covered in
> + Documentation/devicetree/bindings/regulator/regulator.txt
>
> Example:
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-07-11 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 16:04 [PATCH 1/2 RESEND] mfd: arizona: Update DT binding to support LDO1 init_data Charles Keepax
2014-07-10 16:04 ` [PATCH 2/2 RESEND] mfd: arizona: Update DT binding to support MICVDD init_data Charles Keepax
2014-07-11 8:32 ` Lee Jones [this message]
2014-07-11 8:30 ` [PATCH 1/2 RESEND] mfd: arizona: Update DT binding to support LDO1 init_data 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=20140711083227.GL11948@lee--X1 \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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