From: ldewangan@nvidia.com (Laxman Dewangan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dt: tegra: paz00: add regulators
Date: Sat, 4 Aug 2012 00:02:36 +0530 [thread overview]
Message-ID: <501C1944.4030505@nvidia.com> (raw)
In-Reply-To: <1343932593-999-1-git-send-email-swarren@wwwdotorg.org>
On Friday 03 August 2012 12:06 AM, Stephen Warren wrote:
> From: Stephen Warren<swarren@nvidia.com>
>
> The Toshiba AC100/PAZ00 uses a TPS6586x regulator. Instantiate this.
>
> Three data sources were used for the data encoded here:
> * The HW defaults, as extracted from real HW.
> * The schematic, which specifies a voltage for each rail in the signal
> names.
> * The AC100 kernel used by the Ubuntu port:
>
> repo git://gitorious.org/~marvin24/ac100/marvin24s-kernel.git
> branch chromeos-ac100-3.0
> file arch/arm/mach-tegra/board-paz00-power.c
>
> For many rails, the constraints in that tree specified differing min
> and max voltages. In all cases, the min value was ignored, since
> there's no need currently to vary any of the voltages at run-time.
> DVFS might change this in the future.
>
> In most cases these sources all matched. Differences are:
>
> sm0: HW defaults and schematic match at 1.2v. marvin24's kernel had a max
> of 1.3v, but this higher voltage was only applied to HW by DVFS code,
> which isn't currently supported in mainline.
>
> sm1: HW defaults and schematic match at 1.0v. marvin24's kernel had a max
> of 1.125v, but this higher voltage was only applied to HW by DVFS code,
> which isn't currently supported in mainline.
>
> ldo3: The HW default is on. marvin24's kernel didn't specify always-on,
> but since the board wasn't marked as having fully constrained regulators,
> the rail was not turned off, so the difference had no effect. The rail
> is needed for USB.
>
> ldo6: The HW default is 2.85v. The schematics indicate 2.85v. However,
> since this regulator is used for the same purpose as on other boards that
> require 1.8v, this is set to 1.8v. Note that this regulator feeds the CRT
> VDAC on Tegra, and so in practice is unlikely to be used, even though it
> is actaully hooked up in HW.
>
> Portions based on work by Laxman Dewangan<ldewangan@nvidia.com>
>
> Signed-off-by: Stephen Warren<swarren@nvidia.com>
> Tested-by: Marc Dietrich<marvin24@gmx.de> # v2
> ---
Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
>
> + regulators {
> + compatible = "simple-bus";
> + #address-cells =<1>;
> + #size-cells =<0>;
> +
Is "simple-bus" accepted?
Accordingly I need to update for the Cardhu also to have regulator
support which I am going to send.
next prev parent reply other threads:[~2012-08-03 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 18:36 [PATCH] ARM: dt: tegra: paz00: add regulators Stephen Warren
2012-08-03 18:32 ` Laxman Dewangan [this message]
2012-08-03 18:49 ` Stephen Warren
2012-08-10 16:50 ` Stephen Warren
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=501C1944.4030505@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).