From: Kevin Hilman <khilman@deeprootsystems.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Rajendra Nayak <rnayak@ti.com>
Subject: Re: [PATCH 1/2] OMAP2+: PM: initial runtime PM core support
Date: Wed, 08 Sep 2010 10:24:48 -0700 [thread overview]
Message-ID: <871v945esf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100908162143.GD3686@angua.secretlab.ca> (Grant Likely's message of "Wed, 8 Sep 2010 10:21:43 -0600")
Grant Likely <grant.likely@secretlab.ca> writes:
> On Tue, Sep 07, 2010 at 05:54:41PM -0700, Kevin Hilman wrote:
>> From: Kevin Hilman <khilman@ti.com>
>>
>> Implement the new runtime PM framework as a thin layer on top of the
>> omap_device API. OMAP specific runtime PM methods are registered with
>> the as custom methods on the platform_bus.
>>
>> In order to determine if a device is an omap_device, its parent device
>> is checked. All omap_devices have a new 'omap_bus' device as their
>> parent device, so checking for this parent is used to check for valid
>> omap_devices. If a device is an omap_device, then the appropriate
>> omap_device functions are called for it. If not, only the generic
>> runtime PM functions are called.
>>
>> Device driver's ->runtime_idle() hook is called when the runtime PM
>> usecount reaches zero for that device. Driver's ->runtime_suspend()
>> hooks are called just before the device is disabled (via
>> omap_device_idle()), and device driver ->runtime_resume() hooks are
>> called just after device has been enabled (via omap_device_enable().)
>>
>> OMAP4 build support from Rajendra Nayak <rnayak@ti.com>.
>>
>> Cc: Rajendra Nayak <rnayak@ti.com>
>> Signed-off-by: Kevin Hilman <khilman@ti.com>
>
[...]
>> +static int __init omap_pm_runtime_init(void)
>> +{
>> + const struct dev_pm_ops *pm;
>> + struct dev_pm_ops *omap_pm;
>> +
>> + pm = platform_bus_get_pm_ops();
>> + if (!pm) {
>> + pr_err("%s: unable to get dev_pm_ops from platform_bus\n",
>> + __func__);
>> + return -ENODEV;
>> + }
>> +
>> + omap_pm = kmemdup(pm, sizeof(struct dev_pm_ops), GFP_KERNEL);
>> + if (!omap_pm) {
>> + pr_err("%s: unable to alloc memory for new dev_pm_ops\n",
>> + __func__);
>> + return -ENOMEM;
>> + }
>> +
>> + omap_pm->runtime_suspend = omap_pm_runtime_suspend;
>> + omap_pm->runtime_resume = omap_pm_runtime_resume;
>
> This will fail to build when CONFIG_PM_RUNTIME is unset. None of this
> file should be build when CONFIG_PM_RUNTIME=n.
FYI... Rather than not building the whole file, I'm fixing this by
adding an #else clause to the #ifdef:
#else
#define omap_pm_runtime_suspend NULL
#define omap_pm_runtime_resume NULL
#endif /* CONFIG_PM_RUNTIME */
This is because I'll also be building on this to hook up the
_[suspend|resume]_noirq() methods which are based on #ifdef
CONFIG_SUSPEND and not CONFIG_PM_RUNTIME.
Kevin
next prev parent reply other threads:[~2010-09-08 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:54 [PATCH 1/2] OMAP2+: PM: initial runtime PM core support Kevin Hilman
2010-09-08 0:54 ` [PATCH 2/2] OMAP1: PM: add simple runtime PM layer to manage clocks Kevin Hilman
2010-09-08 16:22 ` Grant Likely
2010-09-08 16:21 ` [PATCH 1/2] OMAP2+: PM: initial runtime PM core support Grant Likely
2010-09-08 17:08 ` Kevin Hilman
2010-09-08 17:40 ` Grant Likely
2010-09-08 17:24 ` Kevin Hilman [this message]
2010-09-08 17:39 ` Grant Likely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871v945esf.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox