From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-usb <linux-usb@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH] ARM: dts: Fix musb interrupt for device tree booting
Date: Fri, 10 May 2013 19:55:59 -0700 [thread overview]
Message-ID: <20130511025558.GC28602@atomide.com> (raw)
In-Reply-To: <20130511023557.GB28602@atomide.com>
Commit ad871c10 (ARM: dts: OMAP: Add usb_otg and glue data to
OMAP3+ boards) added support for MUSB on omap3 for device tree,
but added the interrupts the wrong way probably as they were
copied from the omap4.dtsi file. On omap3 we have TI specific
interrupt controller, not GIC.
Fix this by specifying the interrupt following the TI INTC
binding.
Without this fix MUSB won't work as it is trying to use
irq0 instead of irq92.
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
Sorry had the wrong subject in the previous mail. That was
for the breaking commit. Here's the patch again with correct
subject.
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -516,7 +516,7 @@
usb_otg_hs: usb_otg_hs@480ab000 {
compatible = "ti,omap3-musb";
reg = <0x480ab000 0x1000>;
- interrupts = <0 92 0x4>, <0 93 0x4>;
+ interrupts = <92>, <93>;
interrupt-names = "mc", "dma";
ti,hwmods = "usb_otg_hs";
multipoint = <1>;
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Fix musb interrupt for device tree booting
Date: Fri, 10 May 2013 19:55:59 -0700 [thread overview]
Message-ID: <20130511025558.GC28602@atomide.com> (raw)
In-Reply-To: <20130511023557.GB28602@atomide.com>
Commit ad871c10 (ARM: dts: OMAP: Add usb_otg and glue data to
OMAP3+ boards) added support for MUSB on omap3 for device tree,
but added the interrupts the wrong way probably as they were
copied from the omap4.dtsi file. On omap3 we have TI specific
interrupt controller, not GIC.
Fix this by specifying the interrupt following the TI INTC
binding.
Without this fix MUSB won't work as it is trying to use
irq0 instead of irq92.
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
Sorry had the wrong subject in the previous mail. That was
for the breaking commit. Here's the patch again with correct
subject.
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -516,7 +516,7 @@
usb_otg_hs: usb_otg_hs at 480ab000 {
compatible = "ti,omap3-musb";
reg = <0x480ab000 0x1000>;
- interrupts = <0 92 0x4>, <0 93 0x4>;
+ interrupts = <92>, <93>;
interrupt-names = "mc", "dma";
ti,hwmods = "usb_otg_hs";
multipoint = <1>;
next prev parent reply other threads:[~2013-05-11 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 2:35 [PATCH] ARM: dts: OMAP: Add usb_otg and glue data to OMAP3+ boards Tony Lindgren
2013-05-11 2:35 ` Tony Lindgren
2013-05-11 2:55 ` Tony Lindgren [this message]
2013-05-11 2:55 ` [PATCH] ARM: dts: Fix musb interrupt for device tree booting Tony Lindgren
2013-05-15 6:21 ` [PATCH] ARM: dts: OMAP: Add usb_otg and glue data to OMAP3+ boards Kishon Vijay Abraham I
2013-05-15 6:21 ` Kishon Vijay Abraham I
[not found] ` <5193296D.5040001-l0cyMroinI0@public.gmane.org>
2013-05-16 17:46 ` Tony Lindgren
2013-05-16 17:46 ` Tony Lindgren
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=20130511025558.GC28602@atomide.com \
--to=tony@atomide.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.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.