From: Joel Fernandes <joelf@ti.com>
To: Mark Rutland <mark.rutland@arm.com>,
Benoit Cousson <bcousson@baylibre.com>
Cc: Joel Fernandes <joelf@ti.com>,
devicetree@vger.kernel.org,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v3 3/3] ARM: dts: AM33XX: Fix AES interrupt number
Date: Sat, 5 Oct 2013 14:04:37 -0500 [thread overview]
Message-ID: <1380999877-20884-4-git-send-email-joelf@ti.com> (raw)
In-Reply-To: <1380999877-20884-1-git-send-email-joelf@ti.com>
AES interrupts were previously not used, but after recent changes to omap-aes
driver, its being used. We correct the interrupt number to have working PIO
mode.
Signed-off-by: Joel Fernandes <joelf@ti.com>
---
arch/arm/boot/dts/am33xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 2664da9..5c2d6c1 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -724,7 +724,7 @@
compatible = "ti,omap4-aes";
ti,hwmods = "aes";
reg = <0x53500000 0xa0>;
- interrupts = <102>;
+ interrupts = <103>;
dmas = <&edma 6>,
<&edma 5>;
dma-names = "tx", "rx";
--
1.8.1.2
next prev parent reply other threads:[~2013-10-05 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:04 [PATCH v3 0/3] AM33XX crypto DTS patches Joel Fernandes
2013-10-05 19:04 ` [PATCH v3 1/3] ARM: dts: AM33XX: Add SHAM data and documentation Joel Fernandes
2013-10-05 19:04 ` [PATCH v3 2/3] ARM: dts: AM33XX: Add AES " Joel Fernandes
2013-10-05 19:04 ` Joel Fernandes [this message]
[not found] ` <1380999877-20884-1-git-send-email-joelf-l0cyMroinI0@public.gmane.org>
2013-10-08 15:51 ` [PATCH v3 0/3] AM33XX crypto DTS patches Benoit Cousson
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=1380999877-20884-4-git-send-email-joelf@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.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).