On Wed, Oct 5, 2011 at 11:10 AM, Kevin Hilman <khilman@xxxxxx> 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 only see this error on ES2.1 3503 based Overo COMs. So I am wondering if there might be an errata in this area for early 3503 processors? Do you have access to errata that you might check? Or pointers to publicly available errata that I could check? Steve -- 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
