From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 3/4] arm: orion5x: enable xor for orion5x platform
Date: Tue, 26 Mar 2013 21:44:48 +0000 [thread overview]
Message-ID: <1364334289-19669-4-git-send-email-alex@digriz.org.uk> (raw)
In-Reply-To: <1364334289-19669-1-git-send-email-alex@digriz.org.uk>
The orion5x SoC includes DMA functionality, so lets enable that
and turn it on by default.
Signed-off-by: Alexander Clouter <alex@digriz.org.uk>
---
arch/arm/boot/dts/orion5x.dtsi | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/orion5x.dtsi b/arch/arm/boot/dts/orion5x.dtsi
index 6fbc5c0..c37290b 100644
--- a/arch/arm/boot/dts/orion5x.dtsi
+++ b/arch/arm/boot/dts/orion5x.dtsi
@@ -105,6 +105,25 @@
status = "disabled";
};
+ xor at 60900 {
+ compatible = "marvell,orion-xor";
+ reg = <0x60900 0x100
+ 0x60b00 0x100>;
+ status = "okay";
+
+ xor00 {
+ interrupts = <30>;
+ dmacap,memcpy;
+ dmacap,xor;
+ };
+ xor01 {
+ interrupts = <31>;
+ dmacap,memcpy;
+ dmacap,xor;
+ dmacap,memset;
+ };
+ };
+
crypto at 90000 {
compatible = "marvell,orion-crypto";
reg = <0x90000 0x10000>,
--
1.7.10.4
next prev parent reply other threads:[~2013-03-26 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 21:44 [PATCHv3 0/4] arm: orion5x: devicetree fixups and additions Alexander Clouter
2013-03-26 21:44 ` [PATCHv3 1/4] arm: orion5x: fix orion5x.dtsi gpio parameters Alexander Clouter
2013-03-28 17:25 ` Jason Cooper
2013-03-26 21:44 ` [PATCHv3 2/4] arm: orion5x: add ehci bindings to dtsi Alexander Clouter
2013-03-31 0:16 ` Jason Cooper
2013-03-26 21:44 ` Alexander Clouter [this message]
2013-03-31 0:17 ` [PATCHv3 3/4] arm: orion5x: enable xor for orion5x platform Jason Cooper
2013-03-26 21:44 ` [PATCHv3 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa Alexander Clouter
2013-03-28 17:25 ` Jason Cooper
2013-03-26 21:54 ` [PATCHv3 0/4] arm: orion5x: devicetree fixups and additions Andrew Lunn
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=1364334289-19669-4-git-send-email-alex@digriz.org.uk \
--to=alex@digriz.org.uk \
--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).