All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: broonie@opensource.wolfsonmicro.com
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	sameo@linux.intel.com, grant.likely@secretlab.ca,
	rob.herring@calxeda.com, swarren@nvidia.com,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH V3] regulator: tps6586x: add support for SYS rail
Date: Mon, 13 Aug 2012 11:42:57 -0600	[thread overview]
Message-ID: <50293CA1.80900@wwwdotorg.org> (raw)
In-Reply-To: <1344152518-29378-1-git-send-email-ldewangan@nvidia.com>

On 08/05/2012 01:41 AM, Laxman Dewangan wrote:
> Device have SYS rail which is always ON. It is system
> power bus. LDO5 and LDO_RTC get powered through this rail
> internally. Add support for this rail and make the
> LDO5/LDO_RTC input supply to "sys".
> Update document accordingly.

Mark,

This patch appears to have been applied correctly as b93fffb in your
tree, but your for-next branch merge commit f110340 appears to have
dropped the following two hunks:

> diff --git a/Documentation/devicetree/bindings/regulator/tps6586x.txt b/Documentation/devicetree/bindings/regulator/tps6586x.txt
> index d156e1b..ec527d9 100644
> --- a/Documentation/devicetree/bindings/regulator/tps6586x.txt
> +++ b/Documentation/devicetree/bindings/regulator/tps6586x.txt
> @@ -8,7 +8,8 @@ Required properties:
>  - gpio-controller: mark the device as a GPIO controller
>  - regulators: list of regulators provided by this controller, must have
>    property "regulator-compatible" to match their hardware counterparts:
> -  sm[0-2], ldo[0-9] and ldo_rtc
> +  sys, sm[0-2], ldo[0-9] and ldo_rtc
> +- sys-supply: The input supply for SYS.
>  - sm0-supply: The input supply for the SM0.
>  - sm1-supply: The input supply for the SM1.
>  - sm2-supply: The input supply for the SM2.
> @@ -30,6 +34,7 @@ Example:
>  		#gpio-cells = <2>;
>  		gpio-controller;
>  
> +		sys-supply = <&some_reg>;
>  		sm0-supply = <&some_reg>;
>  		sm1-supply = <&some_reg>;
>  		sm2-supply = <&some_reg>;


  parent reply	other threads:[~2012-08-13 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05  7:41 [PATCH V3] regulator: tps6586x: add support for SYS rail Laxman Dewangan
2012-08-05  7:41 ` Laxman Dewangan
2012-08-09 17:10 ` Stephen Warren
2012-08-09 19:04   ` Mark Brown
2012-08-13 17:42 ` Stephen Warren [this message]
2012-08-13 20:04   ` Mark Brown

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=50293CA1.80900@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=sameo@linux.intel.com \
    --cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.