"DebBarma, Tarun Kanti" <[email protected]> writes: > On Fri, Sep 9, 2011 at 11:34 PM, Kevin Hilman <[email protected]> wrote: >> "DebBarma, Tarun Kanti" <[email protected]> writes: >> >>> [...] >>>>> >>>>> +static const struct dev_pm_ops gpio_pm_ops = { >>>>> + .suspend = omap_gpio_suspend, >>>>> + .resume = omap_gpio_resume, >>>>> +}; >>>> >>>> Please use SET_SYSTEM_SLEEP_PM_OPS(). See <linux/pm.h> >>> We can use following macro to initialize .suspend and .resume callbacks. >>> But how do we initialize .runtime_suspend and .runtime_resume callbacks? >>> >>> #define SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \ >>> const struct dev_pm_ops name = { \ >>> SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \ >>> } >>> >>> Do we have something similar to following where we can assign separate >>> pair of callbacks? >> >> SET_RUNTIME_PM_OPS() > Yes, I have done this way: > > static const struct dev_pm_ops gpio_pm_ops = { > SET_SYSTEM_SLEEP_PM_OPS(omap_gpio_suspend, omap_gpio_resume) > SET_RUNTIME_PM_OPS(omap_gpio_runtime_suspend, > omap_gpio_runtime_resume, > NULL)
Perfect. 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
