All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa
Date: Tue, 26 Mar 2013 21:44:49 +0000	[thread overview]
Message-ID: <1364334289-19669-5-git-send-email-alex@digriz.org.uk> (raw)
In-Reply-To: <1364334289-19669-1-git-send-email-alex@digriz.org.uk>

The crypto functionality in the orion5x dtsi uses the Ethernet IRQ and
so things do not work and there is much grumbling at boot time.
The IRQ for the crypto should be 28, and not 22, and that is what this
patch corrects.

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 c37290b..892c64e 100644
--- a/arch/arm/boot/dts/orion5x.dtsi
+++ b/arch/arm/boot/dts/orion5x.dtsi
@@ -129,7 +129,7 @@
 			reg = <0x90000 0x10000>,
 			      <0xf2200000 0x800>;
 			reg-names = "regs", "sram";
-			interrupts = <22>;
+			interrupts = <28>;
 			status = "okay";
 		};
 	};
-- 
1.7.10.4

  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 ` [PATCHv3 3/4] arm: orion5x: enable xor for orion5x platform Alexander Clouter
2013-03-31  0:17   ` Jason Cooper
2013-03-26 21:44 ` Alexander Clouter [this message]
2013-03-28 17:25   ` [PATCHv3 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa 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-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.