> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Basak, Partha > Sent: Wednesday, June 16, 2010 8:10 PM > To: paul@xxxxxxxxx > Cc: khilman@xxxxxxxxxxxxxxxxxxx; Kalliguddi, Hema; Nayak, Rajendra; linux- > omap@xxxxxxxxxxxxxxx > Subject: On the APIs for Enabling and Disabling Wakeup capability. > > Hello Paul, > > 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. We also need the API omap_hwmod_set_slave_idlemode to be exposed as an omap_device API. Net-net, the following APIs which are exported in hwmod layer needs to be wrapped under omap_device_layer as well so that drivers can use them: omap_hwmod_enable_wakeup omap_hwmod_disable_wakeup omap_hwmod_set_slave_idlemode > > 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? > > Thanks to clarify. > Partha > -- > 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 -- 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
