devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Stephen Warren <swarren@nvidia.com>,
	Thomas Abraham <thomas.abraham@linaro.org>
Cc: "devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: [RFC PATCH 2/2] arm/dts: OMAP4: Add dma-controller and dma-request for I2C
Date: Fri, 27 Jan 2012 18:30:05 +0100	[thread overview]
Message-ID: <4F22DF1D.5020904@ti.com> (raw)

Add the DMA controller node.

Add the dma-request attributes for the OMAP4 I2C controllers.

Signed-off-by: Benoit Cousson <b-cousson@ti.com>
Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: Rob Herring <rob.herring@calxeda.com>
---
 arch/arm/boot/dts/omap4.dtsi |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 2938ec8..2425108 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -104,6 +104,13 @@
 			      <0x48240100 0x0100>;
 		};
 
+		sdma: sdma@0 {
+			compatible = "ti,omap4-sdma";
+			ti,hwmods = "dma_system";
+			dma-controller;
+			#dma-cells = <1>;
+		};
+
 		gpio1: gpio@1 {
 			compatible = "ti,omap4-gpio";
 			ti,hwmods = "gpio1";
@@ -205,6 +212,8 @@
 			#address-cells = <1>;
 			#size-cells = <0>;
 			ti,hwmods = "i2c1";
+			dma-request = <&sdma 27>, <&sdma 28>;
+			dma-request-names = "tx", "rx";
 		};
 
 		i2c2: i2c@2 {
@@ -212,6 +221,8 @@
 			#address-cells = <1>;
 			#size-cells = <0>;
 			ti,hwmods = "i2c2";
+			dma-request = <&sdma 29>, <&sdma 30>;
+			dma-request-names = "tx", "rx";
 		};
 
 		i2c3: i2c@3 {
@@ -219,6 +230,8 @@
 			#address-cells = <1>;
 			#size-cells = <0>;
 			ti,hwmods = "i2c3";
+			dma-request = <&sdma 25>, <&sdma 26>;
+			dma-request-names = "tx", "rx";
 		};
 
 		i2c4: i2c@4 {
@@ -226,6 +239,8 @@
 			#address-cells = <1>;
 			#size-cells = <0>;
 			ti,hwmods = "i2c4";
+			dma-request = <&sdma 124>, <&sdma 125>;
+			dma-request-names = "tx", "rx";
 		};
 
 		mcspi1: mcspi@1 {
-- 
1.7.0.4


                 reply	other threads:[~2012-01-27 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F22DF1D.5020904@ti.com \
    --to=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@nvidia.com \
    --cc=thomas.abraham@linaro.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).