From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] ARM: tegra: dalmore: add cpu regulator node
Date: Thu, 21 Mar 2013 18:07:14 +0400 [thread overview]
Message-ID: <514B1412.9060707@cogentembedded.com> (raw)
In-Reply-To: <1363873663-19272-2-git-send-email-ldewangan@nvidia.com>
Hello.
On 21-03-2013 17:47, Laxman Dewangan wrote:
> Dalmore uses the TPS51632 as CPU regulator. The device is connected
> on I2C5.
> Add DT node for TPS51632.
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> arch/arm/boot/dts/tegra114-dalmore.dts | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
> diff --git a/arch/arm/boot/dts/tegra114-dalmore.dts b/arch/arm/boot/dts/tegra114-dalmore.dts
> index a61974e..6be9434 100644
> --- a/arch/arm/boot/dts/tegra114-dalmore.dts
> +++ b/arch/arm/boot/dts/tegra114-dalmore.dts
> @@ -718,6 +718,21 @@
> clock-frequency = <408000000>;
> };
>
> + i2c at 7000d000 {
> + status = "okay";
> + clock-frequency = <400000>;
> +
> + tps51632 {
Should be named "tps51632 at 43" I think.
> + compatible = "ti,tps51632";
> + reg = <0x43>;
WBR, Sergei
next prev parent reply other threads:[~2013-03-21 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:47 [PATCH V2 0/4] ARM: tegra: dalmore: add regulators Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 1/4] ARM: tegra: dalmore: add cpu regulator node Laxman Dewangan
2013-03-21 14:07 ` Sergei Shtylyov [this message]
2013-03-21 17:30 ` Stephen Warren
2013-03-21 13:47 ` [PATCH V2 2/4] ARM: tegra: dalmore: add TPS65090 node Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 3/4] ARM: tegra: dalmore: add fixed regulator node Laxman Dewangan
2013-03-21 13:47 ` [PATCH V2 4/4] ARM: tegra: enable Tegra114 based platform PMICs Laxman Dewangan
2013-03-22 17:37 ` [PATCH V2 0/4] ARM: tegra: dalmore: add regulators 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=514B1412.9060707@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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).