devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
	Jerry Van Baren <vanbaren@cideas.com>,
	Tom Warren <twarren@nvidia.com>
Subject: [PATCH v2 3/7] tegra: fdt: Add extra I2C bindings for U-Boot
Date: Thu, 12 Jan 2012 11:00:14 -0800	[thread overview]
Message-ID: <1326394818-32227-4-git-send-email-sjg@chromium.org> (raw)
In-Reply-To: <1326394818-32227-1-git-send-email-sjg@chromium.org>

Add U-Boot's peripheral clock information to the Tegra20 device tree file.

Signed-off-by: Simon Glass <sjg@chromium.org>
---
Changes in v2:
- Adjust definitions to fit new peripheral clock bindings
- Change 'speed' to 'clock-frequency'
- Remove u-boot,pinmux binding (sadly)

 arch/arm/dts/tegra20.dtsi |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/arch/arm/dts/tegra20.dtsi b/arch/arm/dts/tegra20.dtsi
index ca7b523..963cf27 100644
--- a/arch/arm/dts/tegra20.dtsi
+++ b/arch/arm/dts/tegra20.dtsi
@@ -45,6 +45,8 @@
 		compatible = "nvidia,tegra20-i2c";
 		reg = <0x7000C000 0x100>;
 		interrupts = < 70 >;
+		clock-frequency = <100000>;
+		clocks = <&periph_clk 12>;	// PERIPH_ID_I2C1
 	};
 
 	i2c@7000c400 {
@@ -53,6 +55,8 @@
 		compatible = "nvidia,tegra20-i2c";
 		reg = <0x7000C400 0x100>;
 		interrupts = < 116 >;
+		clock-frequency = <100000>;
+		clocks = <&periph_clk 54>;	// PERIPH_ID_I2C2
 	};
 
 	i2c@7000c500 {
@@ -61,14 +65,18 @@
 		compatible = "nvidia,tegra20-i2c";
 		reg = <0x7000C500 0x100>;
 		interrupts = < 124 >;
+		clock-frequency = <100000>;
+		clocks = <&periph_clk 67>;	// PERIPH_ID_I2C3
 	};
 
 	i2c@7000d000 {
 		#address-cells = <1>;
 		#size-cells = <0>;
-		compatible = "nvidia,tegra20-i2c";
+		compatible = "nvidia,tegra20-i2c-dvc";
 		reg = <0x7000D000 0x200>;
 		interrupts = < 85 >;
+		clock-frequency = <100000>;
+		clocks = <&periph_clk 47>;	// PERIPH_ID_DVC_I2C
 	};
 
 	i2s@70002800 {
-- 
1.7.7.3

  parent reply	other threads:[~2012-01-12 19:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1326394818-32227-1-git-send-email-sjg@chromium.org>
2012-01-12 19:00 ` [PATCH v2 2/7] fdt: Add function to allow aliases to refer to multiple nodes Simon Glass
2012-01-19 20:49   ` Stephen Warren
2012-01-19 23:45     ` Simon Glass
2012-01-20  0:17       ` Stephen Warren
2012-01-20  0:31         ` Simon Glass
2012-01-12 19:00 ` Simon Glass [this message]
2012-01-13  6:31   ` [PATCH v2 3/7] tegra: fdt: Add extra I2C bindings for U-Boot Heiko Schocher
     [not found]     ` <4F0FCFBB.3070407-ynQEQJNshbs@public.gmane.org>
2012-01-13 15:02       ` [U-Boot] " Simon Glass
     [not found]   ` <1326394818-32227-4-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2012-01-19 20:51     ` Stephen Warren
2012-01-22 17:41       ` Simon Glass
     [not found]         ` <CAPnjgZ0cOquTwqg4wx3Cz1+OKXUzYoBvUi2PMA7oHN=2riOHmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-23 18:25           ` Stephen Warren
2012-02-03 23:27             ` Simon Glass

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=1326394818-32227-4-git-send-email-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=twarren@nvidia.com \
    --cc=u-boot@lists.denx.de \
    --cc=vanbaren@cideas.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 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).