* Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> [121015 16:51]: > From: Kevin Hilman <khilman@xxxxxx> > > The runtime PM framework assumes that the hardware state of devices > when initialized is disabled. For all omap_devices, we idle/disable > device by default. However, the console uart uses a "no idle" option > during omap_device init in order to allow earlyprintk usage to work > seamlessly during boot. > > Because the hardware is left partially enabled after init (whatever > the bootloader settings were), the omap_device should later be fully > initialized (including mux) and the runtime PM framework should be > told that the device is active, and not disabled so that the hardware > state is in sync with runtime PM state. > > To fix, after the device has been created/registered, call > omap_device_enable() to finialize init and use pm_runtime_set_active() > to tell the runtime PM core the device is enabled. > > Tested on 2420/n810, 3530/Overo, 3530/Beagle, 3730/OveroSTORM, > 3730/Beagle-xM, 4460/PandaES. > > Reported-by: Paul Walmsley <paul@xxxxxxxxx> > Suggested-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> > Cc: Felipe Balbi <balbi@xxxxxx> > Cc: Sourav Poddar <sourav.poddar@xxxxxx> > Signed-off-by: Kevin Hilman <khilman@xxxxxx> Seems to work for my n800: Tested-by: Tony Lindgren <tony@xxxxxxxxxxx> -- 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
