"Basak, Partha" <[email protected]> writes: > I wanted to close on the introduction of two new OMAP device APIs > omap_device_enable_wakeup () & omap_device_disable_wakeup() in > omap_device layer. > > These APIs are potentially needed by the USB driver (via function > pointers) to work around some USB erratum. > > Alternatively, can we call omap_hwmod_enable_wakeup() via function > pointer? Is it agreeable to call these from driver code (via > function pointers)in some special cases such as to handle some > errata?
Hi Partha, First, we need to dig up the Errata details for that USB problem to better understand the USB-specific issue. In addition, Paul and I discussed the option of automatically managing the wakeup during the hwmod enable/idle, since there isn't really a need to have the wakeup enabled when the hwmod is active. Do you see any disadvantages to that? That would be much cleaner than manually managing the wakeup feature per-driver. 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
