From: Laxman Dewangan <ldewangan@nvidia.com>
To: <swarren@wwwdotorg.org>
Cc: <linux@arm.linux.org.uk>, <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 5/7] ARM: DT: tegra114: Add i2c controller DT entry
Date: Tue, 29 Jan 2013 18:26:21 +0530 [thread overview]
Message-ID: <1359464183-6255-6-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1359464183-6255-1-git-send-email-ldewangan@nvidia.com>
NVIDIA's Tegra114 has 5 i2c controllers. These controllers have
additional feature/configurations to make it functional over
Tegra30's i2c controller driver.
Add DT entry for i2c controllers and make it compatible with
"nvidia,tegra114-i2c".
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
arch/arm/boot/dts/tegra114.dtsi | 45 +++++++++++++++++++++++++++++++++++++++
1 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/tegra114.dtsi b/arch/arm/boot/dts/tegra114.dtsi
index 210b4a7..74d18b2 100644
--- a/arch/arm/boot/dts/tegra114.dtsi
+++ b/arch/arm/boot/dts/tegra114.dtsi
@@ -129,6 +129,51 @@
status = "disabled";
};
+ i2c@7000c000 {
+ compatible = "nvidia,tegra114-i2c";
+ reg = <0x7000c000 0x100>;
+ interrupts = <0 38 0x04>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "disabled";
+ };
+
+ i2c@7000c400 {
+ compatible = "nvidia,tegra114-i2c";
+ reg = <0x7000c400 0x100>;
+ interrupts = <0 84 0x04>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "disabled";
+ };
+
+ i2c@7000c500 {
+ compatible = "nvidia,tegra114-i2c";
+ reg = <0x7000c500 0x100>;
+ interrupts = <0 92 0x04>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "disabled";
+ };
+
+ i2c@7000c700 {
+ compatible = "nvidia,tegra114-i2c";
+ reg = <0x7000c700 0x100>;
+ interrupts = <0 120 0x04>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "disabled";
+ };
+
+ i2c@7000d000 {
+ compatible = "nvidia,tegra114-i2c";
+ reg = <0x7000d000 0x100>;
+ interrupts = <0 53 0x04>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "disabled";
+ };
+
rtc {
compatible = "nvidia,tegra114-rtc", "nvidia,tegra20-rtc";
reg = <0x7000e000 0x100>;
--
1.7.1.1
next prev parent reply other threads:[~2013-01-29 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 12:56 [PATCH 0/7] ARM: DT: tegra114: add dt entry for gpio/pinmux/dma/i2c/serial/kbc Laxman Dewangan
2013-01-29 12:56 ` [PATCH 1/7] ARM: tegra114: select PINCTRL for Tegra114 SoC Laxman Dewangan
2013-01-29 12:56 ` [PATCH 2/7] ARM: DT: tegra114: add GPIO DT entry Laxman Dewangan
2013-01-29 12:56 ` [PATCH 3/7] ARM: DT: tegra114: add APB DMA controller " Laxman Dewangan
2013-01-29 17:42 ` Stephen Warren
2013-01-30 3:54 ` Laxman Dewangan
2013-01-30 4:01 ` Stephen Warren
2013-01-29 12:56 ` [PATCH 4/7] ARM: DT: tegra114: add pinmux " Laxman Dewangan
2013-01-29 12:56 ` Laxman Dewangan [this message]
2013-01-29 12:56 ` [PATCH 6/7] ARM: DT: tegra114:add aliases and DMA requestor for serial controller Laxman Dewangan
2013-01-29 18:10 ` Stephen Warren
2013-01-29 12:56 ` [PATCH 7/7] ARM: DT: tegra114: add KBC controller DT entry 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=1359464183-6255-6-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=swarren@wwwdotorg.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).