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: sta...@vger.kernel.org
Cc: mturque...@baylibre.com
Cc: sb...@codeaurora.org
Cc: linux-...@vger.kernel.org
Cc: linux-omap@vger.kernel.org
Cc: t-kri...@ti.com
Cc: linux-ker...@lists.codethink.co.uk
Signed-off-by: Ben Dooks <ben.do...@codethink.co.uk>
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
initial clock conversion commit as a fixes by for this:
commit aafd900cab87d339dc3004c241eebc854005124b
Author: Tero Kristo <t-kri...@ti.com>
Date: Fri Aug 2 14:04:19 2013 +0300
CLK: TI: add omap3 clock init file
I'll add a fixes tag to this and queue it for 4.3-rc-fixes.
-Tero
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
