* Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> [101011 07:37]: > Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: > > > > This is happening because 'omap_serial_init()' is hanging in the boot. > > On OMAP3 the watchdog is generating reboot because devices_init doesn't > > happens where as on OMAP4 it just hangs without reboot. > > The uart clock is not getting enabled after omap_device_idle as part > > of omap_serial_init. > > The omap_device_idle(will disable the clock) then omap_uart_block_sleep() > > should enable clock back disabled during the boot up phase. > > But omap_uart_block_sleep() stuffed version is binded only under > > CONFIG_PM and other version is just empty. Hence it is not enabling > > clock back as expected > > > > This patch adds uart clock enable code to omap_uart_block_sleep() function > > built with CONFIG_PM disabled. > > Thanks to Charulatha and Govindraj for their help on this debug. > > > > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > Signed-off-by: Charulatha V <charu@xxxxxx> > > Signed-off-by: Govindraj.R <govindraj.raja@xxxxxx> > > > Acked-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > > This is a regression fix, so we should queue this for 2.6.37. Thanks, adding to omap-for-linus. Regards, Tony -- 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
