summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/omap54xx-clocks.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2014-08-26 01:15:35 +0200
committerTony Lindgren <tony@atomide.com>2014-08-26 01:15:35 +0200
commitcc824534d4fef0e46e4486d5c1e10d3c6b1ebadc (patch)
tree70d41e161d5c99b20cb75579e98940bbe3da94b0 /arch/arm/boot/dts/omap54xx-clocks.dtsi
parentARM: dts: Enable UART wake-up events for beagleboard (diff)
downloadlinux-cc824534d4fef0e46e4486d5c1e10d3c6b1ebadc.tar.xz
linux-cc824534d4fef0e46e4486d5c1e10d3c6b1ebadc.zip
ARM: OMAP2+: hwmod: Rearm wake-up interrupts for DT when MUSB is idled
Looks like MUSB cable removal can cause wake-up interrupts to stop working for device tree based booting at least for UART3 even as nothing is dynamically remuxed. This can be fixed by calling reconfigure_io_chain() for device tree based booting in hwmod code. Note that we already do that for legacy booting if the legacy mux is configured. My guess is that this is related to UART3 and MUSB ULPI hsusb0_data0 and hsusb0_data1 support for Carkit mode that somehow affect the configured IO chain for UART3 and require rearming the wake-up interrupts. In general, for device tree based booting, pinctrl-single calls the rearm hook that in turn calls reconfigure_io_chain so calling reconfigure_io_chain should not be needed from the hwmod code for other events. So let's limit the hwmod rearming of iochain only to HWMOD_FORCE_MSTANDBY where MUSB is currently the only user of it. If we see other devices needing similar changes we can add more checks for it. Cc: Paul Walmsley <paul@pwsan.com> Cc: stable@vger.kernel.org # v3.16 Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/omap54xx-clocks.dtsi')
0 files changed, 0 insertions, 0 deletions