On Wed, 5 Oct 2011, Kevin Hilman wrote: > The need to comment this out suggests that omap3_has_io_wakeup() is > returning true for this SoC but should not. > > Looking at mach-omap2/io.c, that feature flag is not set on the 3505 and > 3517, but is set on the 3503: > > if (!cpu_is_omap3505() && !cpu_is_omap3517()) > omap_features |= OMAP3_HAS_IO_WAKEUP; > > Adding a case for the 3503 here should fix this problem. > > Maybe check other checks for cpu_is_omap3505() and see if those should > also be checking for the 3503.
I think 3503 supports I/O wakeup, but just doesn't support the I/O chain enable sequence. So as I understand it, there's a window where wakeup events could be lost. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
