From: Joel Fernandes <joelf@ti.com>
To: Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Benoit Cousson <bcousson@baylibre.com>
Cc: Joel Fernandes <joelf@ti.com>, Tony Lindgren <tony@atomide.com>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Russell King <linux@arm.linux.org.uk>,
"open list:OMAP DEVICE TREE..." <devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 2/9] omap4: dts: Add node for DES3DES module
Date: Mon, 30 Sep 2013 10:12:59 -0500 [thread overview]
Message-ID: <1380553986-15910-3-git-send-email-joelf@ti.com> (raw)
In-Reply-To: <1380553986-15910-1-git-send-email-joelf@ti.com>
OMAP4 has an DES3DES module that uses the omap-des crypto driver.
Add DT entries for the same.
Signed-off-by: Joel Fernandes <joelf@ti.com>
---
arch/arm/boot/dts/omap4.dtsi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 16a44d6..6be1f56 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -672,5 +672,14 @@
dmas = <&sdma 111>, <&sdma 110>;
dma-names = "tx", "rx";
};
+
+ des: des@480a5000 {
+ compatible = "ti,omap4-des";
+ ti,hwmods = "des";
+ reg = <0x480a5000 0xa0>;
+ interrupts = <GIC_SPI 82 IRQ_TYPE_LEVEL_HIGH>;
+ dmas = <&sdma 117>, <&sdma 116>;
+ dma-names = "tx", "rx";
+ };
};
};
--
1.8.1.2
next prev parent reply other threads:[~2013-09-30 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380553986-15910-1-git-send-email-joelf@ti.com>
2013-09-30 15:12 ` [PATCH v2 1/9] omap4: dts: Add node for AES Joel Fernandes
2013-09-30 15:12 ` Joel Fernandes [this message]
2013-09-30 15:13 ` [PATCH v2 3/9] ARM: dts: Add SHAM data and documentation for AM33XX Joel Fernandes
2013-10-04 14:26 ` Mark Rutland
2013-10-05 18:18 ` Joel Fernandes
2013-09-30 15:13 ` [PATCH v2 4/9] ARM: dts: Add AES " Joel Fernandes
[not found] ` <1380553986-15910-5-git-send-email-joelf-l0cyMroinI0@public.gmane.org>
2013-10-04 14:33 ` Mark Rutland
2013-10-05 18:29 ` Joel Fernandes
2013-09-30 15:13 ` [PATCH v2 5/9] am33xx: dts: Fix AES interrupt number Joel Fernandes
2013-10-04 14:19 ` Benoit Cousson
2013-09-30 15:13 ` [PATCH v2 6/9] ARM: am437x: dts: Add AES node for am437x Joel Fernandes
2013-09-30 15:13 ` [PATCH v2 7/9] ARM: am437x: dts: Add DES " Joel Fernandes
2013-09-30 15:13 ` [PATCH v2 8/9] ARM: dts: AM33XX: Add LCDC info into am335x-evm Joel Fernandes
2013-09-30 15:13 ` [PATCH v2 9/9] dts: boneblack: add pinmux and hdmi node to enable display Joel Fernandes
2013-10-03 13:25 ` [PATCH v2 0/9] ARM: dts: DT data for OMAP platforms for v3.13 Benoit Cousson
2013-10-04 2:00 ` Joel Fernandes
2013-10-04 14:10 ` Benoit Cousson
2013-10-04 14:50 ` Joel Fernandes
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=1380553986-15910-3-git-send-email-joelf@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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).