Dave Hylands <[email protected]> writes:
> Hi,
>
> I have an older overo board, which has an OMAP3503
>
> U-booot reports:
> OMAP3503-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
>
> In order to get the 2.6.39 kernel to boot, I had to make 2 modifications:
>
> In arch/arm/mach-omap2/pm34xx.c, in the omap_sram_idle routine I had
> to put an #if 0 around:
>
> #if 0
> if (omap3_has_io_wakeup() &&
> (per_next_state < PWRDM_POWER_ON ||
> core_next_state < PWRDM_POWER_ON)) {
> omap2_prm_set_mod_reg_bits(OMAP3430_EN_IO_MASK,
> WKUP_MOD, PM_WKEN);
> omap3_enable_io_chain();
> }
> #endif
>
> or I would get continuous
>
> Wake up daisy chain activation failed.
>
> messages on the console.
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.
Kevin
--
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
