From: Paul Cercueil <paul@crapouillou.net>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
list@opendingux.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/8] PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros
Date: Wed, 05 Jan 2022 10:15:36 +0000 [thread overview]
Message-ID: <06F85R.46PNU7YFWD631@crapouillou.net> (raw)
In-Reply-To: <20220105100332.000001c1@Huawei.com>
Hi Jonathan,
Le mer., janv. 5 2022 at 10:03:32 +0000, Jonathan Cameron
<Jonathan.Cameron@Huawei.com> a écrit :
> On Tue, 4 Jan 2022 21:42:09 +0000
> Paul Cercueil <paul@crapouillou.net> wrote:
>
>> These macros are defined conditionally, according to CONFIG_PM:
>> - if CONFIG_PM is enabled, these macros resolve to
>> DEFINE_SIMPLE_DEV_PM_OPS(), and the dev_pm_ops symbol will be
>> exported.
>>
>> - if CONFIG_PM is disabled, these macros will result in a dummy
>> static
>> dev_pm_ops to be created with the __maybe_unused flag. The
>> dev_pm_ops
>> will then be discarded by the compiler, along with the provided
>> callback functions if they are not used anywhere else.
>>
>> In the second case, the symbol is not exported, which should be
>> perfectly fine - users of the symbol should all use the pm_ptr() or
>> pm_sleep_ptr() macro, so the dev_pm_ops marked as "extern" in the
>> client's code will never be accessed.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>> include/linux/pm.h | 33 ++++++++++++++++++++++++++++++---
>> 1 file changed, 30 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/linux/pm.h b/include/linux/pm.h
>> index 389e600df233..a1ce29566aea 100644
>> --- a/include/linux/pm.h
>> +++ b/include/linux/pm.h
>> @@ -8,6 +8,7 @@
>> #ifndef _LINUX_PM_H
>> #define _LINUX_PM_H
>>
>> +#include <linux/export.h>
>> #include <linux/list.h>
>> #include <linux/workqueue.h>
>> #include <linux/spinlock.h>
>> @@ -357,14 +358,40 @@ struct dev_pm_ops {
>> #define SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn)
>> #endif
>>
>> +#define _DEFINE_DEV_PM_OPS(name, \
>> + suspend_fn, resume_fn, \
>> + runtime_suspend_fn, runtime_resume_fn, idle_fn) \
>> +const struct dev_pm_ops name = { \
>> + SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
>> + RUNTIME_PM_OPS(runtime_suspend_fn, runtime_resume_fn, idle_fn) \
>> +}
>> +
>
> one blank line probably enough.
>
>> +
>> /*
>> * Use this if you want to use the same suspend and resume
>> callbacks for suspend
>> * to RAM and hibernation.
>> */
>> #define DEFINE_SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
>> -const struct dev_pm_ops name = { \
>> - SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
>> -}
>> + _DEFINE_DEV_PM_OPS(name, suspend_fn, resume_fn, NULL, NULL, NULL)
>> +
>> +#ifdef CONFIG_PM
>> +#define _EXPORT_DEV_PM_OPS(name, suspend_fn, resume_fn,
>> runtime_suspend_fn, \
>> + runtime_resume_fn, idle_fn, sec) \
>> + _DEFINE_DEV_PM_OPS(name, suspend_fn, resume_fn,
>> runtime_suspend_fn, \
>> + runtime_resume_fn, idle_fn); \
>> + _EXPORT_SYMBOL(name, sec)
>> +#else
>> +#define _EXPORT_DEV_PM_OPS(name, suspend_fn, resume_fn,
>> runtime_suspend_fn, \
>> + runtime_resume_fn, idle_fn, sec) \
>> +static __maybe_unused _DEFINE_DEV_PM_OPS(__static_##name,
>> suspend_fn, \
>> + resume_fn, runtime_suspend_fn, \
>> + runtime_resume_fn, idle_fn)
>> +#endif
>> +
>> +#define EXPORT_SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
>> + _EXPORT_DEV_PM_OPS(name, suspend_fn, resume_fn, NULL, NULL, NULL,
>> "")
>> +#define EXPORT_GPL_SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
>> + _EXPORT_DEV_PM_OPS(name, suspend_fn, resume_fn, NULL, NULL, NULL,
>> "_gpl")
>
> So you can get away with these two cases because the
> SYSTEM_SLEEP_PM_OPS() all have
> pm_sleep_ptr() wrappers. However, _EXPORT_DEV_PM_OPS() could be used
> directly and
> would require __maybe_unused for the RUNTIME_PM_OPS() parameters
> which isn't ideal.
I don't see why. On both cases (CONFIG_PM enabled/disabled) the
runtime-PM callbacks are referenced directly, so at no point do they
appear as unused; therefore __maybe_unused is not needed.
Cheers,
-Paul
> Maybe I'm missing some reason that isn't a problem though as easy to
> get lost in
> these macros. :)
>
> You could argue that the _ is meant to indicate that macro shouldn't
> be used directly
> but I'm not that optimistic.
>
> Jonathan
>
>
>
>>
>> /* Deprecated. Use DEFINE_SIMPLE_DEV_PM_OPS() instead. */
>> #define SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
>
next prev parent reply other threads:[~2022-01-05 10:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 21:42 [PATCH 0/8] DEV_PM_OPS macros rework Paul Cercueil
2022-01-04 21:42 ` [PATCH 1/8] PM: core: Remove DEFINE_UNIVERSAL_DEV_PM_OPS() macro Paul Cercueil
2022-01-05 9:52 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 2/8] PM: core: Remove static qualifier in DEFINE_SIMPLE_DEV_PM_OPS macro Paul Cercueil
2022-01-05 9:54 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 3/8] PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros Paul Cercueil
2022-01-05 10:03 ` Jonathan Cameron
2022-01-05 10:15 ` Paul Cercueil [this message]
2022-01-05 10:48 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 4/8] PM: runtime: Add DEFINE_RUNTIME_DEV_PM_OPS() macro Paul Cercueil
2022-01-05 10:05 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 5/8] PM: runtime: Add EXPORT[_GPL]_RUNTIME_DEV_PM_OPS macros Paul Cercueil
2022-01-05 10:07 ` Jonathan Cameron
2022-01-05 10:49 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 6/8] mmc: mxc: Make dev_pm_ops struct static Paul Cercueil
2022-01-05 10:12 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 7/8] mmc: jz4740: " Paul Cercueil
2022-01-05 10:12 ` Jonathan Cameron
2022-01-04 21:42 ` [PATCH 8/8] iio: gyro: mpu3050: Use new PM macros Paul Cercueil
2022-01-05 10:11 ` Jonathan Cameron
2022-01-05 10:17 ` Paul Cercueil
2022-01-05 10:17 ` [PATCH 0/8] DEV_PM_OPS macros rework Jonathan Cameron
2022-01-05 16:32 ` Paul Cercueil
2022-01-05 17:37 ` Rafael J. Wysocki
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=06F85R.46PNU7YFWD631@crapouillou.net \
--to=paul@crapouillou.net \
--cc=Jonathan.Cameron@Huawei.com \
--cc=arnd@arndb.de \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=len.brown@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=list@opendingux.net \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.org \
/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
Powered by JetHome