Found this chip init problem while debugging a problem with usb host getting stuck at active mode when toggling the /sys/power/enable_off_mode. The OMAP_CHIP_INIT calls used "is ES2.0" macros, while it should be now according to the new macro definitions "greater or equal to ES2.0". Boot tested on RX51 (smartreflex disabled, as there is that problem vp_init problem) Should apply on latest pm branch. - Kalle -- 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
