From: Paul Cercueil <paul@crapouillou.net>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
od@zcrc.me, linux-pm@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Paul Cercueil <paul@crapouillou.net>
Subject: [RFC PATCH 1/3] PM: introduce pm_ptr() and pm_sleep_ptr()
Date: Tue, 11 Feb 2020 13:03:19 -0300 [thread overview]
Message-ID: <20200211160321.22124-2-paul@crapouillou.net> (raw)
In-Reply-To: <20200211160321.22124-1-paul@crapouillou.net>
These macros are analogous to the infamous of_match_ptr(). If CONFIG_PM
or CONFIG_PM_SLEEP are enabled (respectively), these macros will resolve
to their argument, otherwise to NULL.
Signed-off-by: Paul Cercueil <paul@crapouillou.net>
---
include/linux/pm.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/include/linux/pm.h b/include/linux/pm.h
index e057d1fa2469..1e183d78a1ae 100644
--- a/include/linux/pm.h
+++ b/include/linux/pm.h
@@ -374,6 +374,18 @@ const struct dev_pm_ops name = { \
SET_RUNTIME_PM_OPS(suspend_fn, resume_fn, idle_fn) \
}
+#ifdef CONFIG_PM
+#define pm_ptr(_ptr) (_ptr)
+#else
+#define pm_ptr(_ptr) NULL
+#endif
+
+#ifdef CONFIG_PM_SLEEP
+#define pm_sleep_ptr(_ptr) (_ptr)
+#else
+#define pm_sleep_ptr(_ptr) NULL
+#endif
+
/*
* PM_EVENT_ messages
*
--
2.25.0
next prev parent reply other threads:[~2020-02-11 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:03 [RFC PATCH 0/3] Introduce pm_ptr() / pm_sleep_ptr() Paul Cercueil
2020-02-11 16:03 ` Paul Cercueil [this message]
2020-02-11 16:03 ` [RFC PATCH 2/3] PM: Make *_DEV_PM_OPS macros use __maybe_unused Paul Cercueil
2020-02-11 16:03 ` [RFC PATCH 3/3] mmc: jz4740: Use pm_sleep_ptr() macro Paul Cercueil
2020-02-20 13:38 ` Ulf Hansson
2020-02-20 13:42 ` Ulf Hansson
2020-02-24 15:41 ` Paul Cercueil
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=20200211160321.22124-2-paul@crapouillou.net \
--to=paul@crapouillou.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=od@zcrc.me \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).