On 02/10/15 07:07, Tero Kristo wrote: > On 10/02/2015 03:15 AM, Stephen Boyd wrote: >> On 09/29, Ben Dooks wrote: >>> On the OMAP AM3517 platform the uart4_ick gets registered >>> twice, causing any power managment to /dev/ttyO3 to fail >>> when trying to wake the device up. >>> >>> This solves the following oops: >>> >>> [] Unhandled fault: external abort on non-linefetch (0x1028) at >>> 0xfa09e008 >>> [] PC is at serial_omap_pm+0x48/0x15c >>> [] LR is at _raw_spin_unlock_irqrestore+0x30/0x5c >>> >>> Cc: stable@xxxxxxxxxxxxxxx >>> Cc: mturquette@xxxxxxxxxxxx >>> Cc: sboyd@xxxxxxxxxxxxxx >>> Cc: linux-clk@xxxxxxxxxxxxxxx >>> Cc: linux-omap@xxxxxxxxxxxxxxx >>> Cc: t-kristo@xxxxxx >>> Cc: linux-kernel@xxxxxxxxxxxxxxxxxxxxx >>> Signed-off-by: Ben Dooks <ben.dooks@xxxxxxxxxxxxxxx> >> >> Which patch broke this? Adding a Fixes: line will help us figure >> out where to backport this. >> > > The issue has been around since the legacy clock data code already, I am > not quite sure which initially broke it though. As such, we can use the Thanks, i've been off ill for the last two days so catching up on this. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
