From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa
Date: Sat, 23 Mar 2013 22:29:57 +0000 [thread overview]
Message-ID: <1364077797-21206-5-git-send-email-alex@digriz.org.uk> (raw)
In-Reply-To: <1364077797-21206-1-git-send-email-alex@digriz.org.uk>
The crypto functionality hook in the orion5x dtsi uses an IRQ that clashes
with the Ethernet controller, so lets move it to use the IRQ that the non-DT
code utilises.
Signed-off-by: Alexander Clouter <alex@digriz.org.uk>
---
arch/arm/boot/dts/orion5x.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/orion5x.dtsi b/arch/arm/boot/dts/orion5x.dtsi
index 3944b9b..f4be4c5 100644
--- a/arch/arm/boot/dts/orion5x.dtsi
+++ b/arch/arm/boot/dts/orion5x.dtsi
@@ -127,7 +127,7 @@
reg = <0x90000 0x10000>,
<0xf2200000 0x800>;
reg-names = "regs", "sram";
- interrupts = <22>;
+ interrupts = <28>;
status = "okay";
};
};
--
1.7.10.4
next prev parent reply other threads:[~2013-03-23 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 22:29 [PATCHv2 0/4] arm: orion5x: devicetree fixups and additions Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 1/4] arm: orion5x: fix orion5x.dtsi gpio parameters Alexander Clouter
2013-03-25 8:43 ` Andrew Lunn
2013-03-26 21:02 ` Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 2/4] arm: orion5x: add ehci bindings to dtsi Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 3/4] arm: orion5x: enable xor for orion5x platform Alexander Clouter
2013-03-23 22:29 ` Alexander Clouter [this message]
2013-03-25 8:47 ` [PATCHv2 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa Andrew Lunn
2013-03-26 21:02 ` Alexander Clouter
2013-03-24 9:48 ` [PATCHv2 0/4] arm: orion5x: devicetree fixups and additions Arnd Bergmann
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=1364077797-21206-5-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).