summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/logicpd-som-lv.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2017-11-17 19:56:58 +0300
committerTony Lindgren <tony@atomide.com>2017-11-28 18:04:44 +0300
commitcf87634c8b24e24bf379b8c6807c8b0fb5f23567 (patch)
tree02cb74682c0f53ec3e8c7d4524a81a5959ee138a /arch/arm/boot/dts/logicpd-som-lv.dtsi
parent4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323 (diff)
downloadlinux-cf87634c8b24e24bf379b8c6807c8b0fb5f23567.tar.xz
ARM: dts: Fix omap4 hang with GPS connected to USB by using wakeupgen
There's been a reproducable USB OHCI/EHCI cpuidle related hang on omap4 for a while that happens after about 20 - 40 minutes on an idle system with some data feeding device being connected, like a USB GPS device or a cellular modem. This issue happens in cpuidle states C2 and C3 and does not happen if cpuidle is limited to C1 state only. The symptoms are that the whole system hangs and never wakes up from idle, and if a watchdog is configured the system reboots after a while. Turns out that OHCI/EHCI devices on omap4 are trying to use the GIC interrupt controller directly as a parent instead of the WUGEN. We need to pass the interrupts through WUGEN to GIC to provide the wakeup events for the processor. Let's fix the issue by removing the gic interrupt-parent and use the default interrupt-parent wakeupgen instead. Note that omap5.dtsi had this already fixes earlier by commit 7136d457f365 ("ARM: omap: convert wakeupgen to stacked domains") but we somehow missed omap4 at that point. Fixes: 7136d457f365 ("ARM: omap: convert wakeupgen to stacked domains") Cc: Dave Gerlach <d-gerlach@ti.com> Cc: Nishanth Menon <nm@ti.com> Cc: Marc Zyngier <marc.zyngier@arm.com> Cc: Sebastian Reichel <sebastian.reichel@collabora.co.uk> Reviewed-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/logicpd-som-lv.dtsi')
0 files changed, 0 insertions, 0 deletions