From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: broonie@opensource.wolfsonmicro.com, ccross@android.com,
olof@lixom.net, lrg@ti.com, thierry.reding@avionic-design.de,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
rob.herring@calxeda.com, grant.likely@secretlab.ca
Subject: Re: [PATCH 2/2] regulator: tps6586x: add support for input supply
Date: Mon, 23 Jul 2012 14:51:44 -0600 [thread overview]
Message-ID: <500DB960.6020802@wwwdotorg.org> (raw)
In-Reply-To: <1342187432-18668-3-git-send-email-ldewangan@nvidia.com>
On 07/13/2012 07:50 AM, Laxman Dewangan wrote:
> There is multiple voltage input pins on device which
> takes the voltage input for different voltage regulator.
> Support to configure the voltage input supplied by
> different regulator for each regulators.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> .../devicetree/bindings/regulator/tps6586x.txt | 17 +++++++
> drivers/regulator/tps6586x-regulator.c | 47 ++++++++++---------
> 2 files changed, 42 insertions(+), 22 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/regulator/tps6586x.txt b/Documentation/devicetree/bindings/regulator/tps6586x.txt
> index ab17ef6..d156e1b 100644
> --- a/Documentation/devicetree/bindings/regulator/tps6586x.txt
> +++ b/Documentation/devicetree/bindings/regulator/tps6586x.txt
> @@ -9,6 +9,14 @@ Required properties:
> - 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
> +- sm0-supply: The input supply for the SM0.
> +- sm1-supply: The input supply for the SM1.
> +- sm2-supply: The input supply for the SM2.
> +- vinldo01-supply: The input supply for the LDO1 and LDO2
> +- vinldo23-supply: The input supply for the LDO2 and LDO3
> +- vinldo4-supply: The input supply for the LDO4
> +- vinldo678-supply: The input supply for the LDO6, LDO7 and LDO8
> +- vinldo9-supply: The input supply for the LDO9
Hmm. The signal names in my data sheet are VIN_SMn and VINLDOn, so
having "vin" in just some of the property names seems a little inconsistent.
> diff --git a/drivers/regulator/tps6586x-regulator.c b/drivers/regulator/tps6586x-regulator.c
> static inline struct device *to_tps6586x_dev(struct regulator_dev *rdev)
> {
> - return rdev_get_dev(rdev)->parent->parent;
> + return rdev_get_dev(rdev)->parent;
...
> @@ -351,7 +354,7 @@ static int __devinit tps6586x_regulator_probe(struct platform_device *pdev)
...
> - config.dev = &pdev->dev;
> + config.dev = pdev->dev.parent;
Those seem like unrelated changes, but I suppose it's fine.
next prev parent reply other threads:[~2012-07-23 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:50 [PATCH 0/2] regulator: tps6586x: support for input supply Laxman Dewangan
[not found] ` <1342187432-18668-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-13 13:50 ` [PATCH 1/2] ARM: tegra: harmony: add regulator supply name and its " Laxman Dewangan
[not found] ` <1342187432-18668-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-23 20:49 ` Stephen Warren
2012-07-13 13:50 ` [PATCH 2/2] regulator: tps6586x: add support for " Laxman Dewangan
2012-07-13 14:22 ` Mark Brown
[not found] ` <20120713142229.GM4215-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-13 17:15 ` Laxman Dewangan
2012-07-15 21:21 ` Mark Brown
[not found] ` <20120715212114.GI4041-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-23 20:54 ` Stephen Warren
[not found] ` <500DBA1F.7050605-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-23 21:30 ` Mark Brown
2012-07-23 20:51 ` Stephen Warren [this message]
[not found] ` <500DB960.6020802-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-23 21:29 ` Mark Brown
2012-07-24 4:29 ` Laxman Dewangan
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=500DB960.6020802@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ccross@android.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=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=thierry.reding@avionic-design.de \
/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;
as well as URLs for NNTP newsgroup(s).