From: Paul Cercueil <paul@crapouillou.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2 01/30] pm: Improve EXPORT_*_DEV_PM_OPS macros
Date: Tue, 04 Oct 2022 20:12:56 +0100 [thread overview]
Message-ID: <KDT8JR.QPETUDEUEUK4@crapouillou.net> (raw)
In-Reply-To: <CAJZ5v0i06Nj1+kWDPtok-3vB1UPKfdieux8VrLm21NT0XFCftA@mail.gmail.com>
Le mar., oct. 4 2022 at 20:54:28 +0200, Rafael J. Wysocki
<rafael@kernel.org> a écrit :
> On Sun, Oct 2, 2022 at 1:18 PM Paul Cercueil <paul@crapouillou.net>
> wrote:
>>
>>
>>
>> Le sam., oct. 1 2022 at 18:01:30 +0100, Jonathan Cameron
>> <jic23@kernel.org> a écrit :
>> > On Mon, 26 Sep 2022 15:35:35 +0200
>> > "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>> >
>> >> On Mon, Sep 26, 2022 at 3:27 PM Paul Cercueil
>> >> <paul@crapouillou.net> wrote:
>> >> >
>> >> > Hi,
>> >> >
>> >> > Le lun., sept. 26 2022 at 14:00:52 +0200, Rafael J. Wysocki
>> >> > <rafael@kernel.org> a écrit :
>> >> > > On Sun, Sep 25, 2022 at 4:52 PM Jonathan Cameron
>> >> <jic23@kernel.org>
>> >> > > wrote:
>> >> > >>
>> >> > >> On Thu, 25 Aug 2022 23:42:53 +0100
>> >> > >> Paul Cercueil <paul@crapouillou.net> wrote:
>> >> > >>
>> >> > >> > Hi Rafael,
>> >> > >> >
>> >> > >> > Le mar., août 23 2022 at 19:47:57 +0200, Rafael J.
>> Wysocki
>> >> > >> > <rafael@kernel.org> a écrit :
>> >> > >> > > On Mon, Aug 8, 2022 at 7:41 PM Paul Cercueil
>> >> > >> <paul@crapouillou.net>
>> >> > >> > > wrote:
>> >> > >> > >>
>> >> > >> > >> Update the _EXPORT_DEV_PM_OPS() internal macro. It
>> was
>> >> not
>> >> > >> used
>> >> > >> > >> anywhere
>> >> > >> > >> outside pm.h and pm_runtime.h, so it is safe to
>> update
>> >> it.
>> >> > >> > >>
>> >> > >> > >> Before, this macro would take a few parameters to be
>> >> used as
>> >> > >> sleep
>> >> > >> > >> and
>> >> > >> > >> runtime callbacks. This made it unsuitable to use
>> with
>> >> > >> different
>> >> > >> > >> callbacks, for instance the "noirq" ones.
>> >> > >> > >>
>> >> > >> > >> It is now semantically different: instead of
>> creating a
>> >> > >> > >> conditionally
>> >> > >> > >> exported dev_pm_ops structure, it only contains
>> part of
>> >> the
>> >> > >> > >> definition.
>> >> > >> > >>
>> >> > >> > >> This macro should however never be used directly
>> (hence
>> >> the
>> >> > >> trailing
>> >> > >> > >> underscore). Instead, the following four macros are
>> >> provided:
>> >> > >> > >> - EXPORT_DEV_PM_OPS(name)
>> >> > >> > >> - EXPORT_GPL_DEV_PM_OPS(name)
>> >> > >> > >> - EXPORT_NS_DEV_PM_OPS(name, ns)
>> >> > >> > >> - EXPORT_NS_GPL_DEV_PM_OPS(name, ns)
>> >> > >> > >>
>> >> > >> > >> For instance, it is now possible to conditionally
>> >> export noirq
>> >> > >> > >> suspend/resume PM functions like this:
>> >> > >> > >>
>> >> > >> > >> EXPORT_GPL_DEV_PM_OPS(foo_pm_ops) = {
>> >> > >> > >> NOIRQ_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn)
>> >> > >> > >> };
>> >> > >> > >>
>> >> > >> > >> The existing helper macros
>> EXPORT_*_SIMPLE_DEV_PM_OPS()
>> >> and
>> >> > >> > >> EXPORT_*_RUNTIME_DEV_PM_OPS() have been updated to
>> use
>> >> these
>> >> > >> new
>> >> > >> > >> macros.
>> >> > >> > >>
>> >> > >> > >> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> >> > >> > >
>> >> > >> > > Acked-by: Rafael J. Wysocki
>> <rafael.j.wysocki@intel.com>
>> >> > >> > >
>> >> > >> > > or please let me know if you need me to pick up this
>> one.
>> >> > >> >
>> >> > >> > Could you pick this one up then, and make a branch for
>> >> Jonathan?
>> >> > >>
>> >> > >> Hi Paul, Rafael,
>> >> > >>
>> >> > >> What happened to this in the end? I can't immediately
>> find
>> >> it on
>> >> > >> any of the pm git tree branches.
>> >> > >>
>> >> > >> At this stage in the cycle it would be great if this
>> patch at
>> >> least
>> >> > >> makes the merge window, so we can make use of it next
>> cycle.
>> >> > >
>> >> > > I thought that this would go in along with the other
>> patches in
>> >> the
>> >> > > series.
>> >> > >
>> >> > > I can apply it directly, though, if needed.
>> >> > >
>> >> > > Thanks!
>> >> >
>> >> > I think at this point Jonathan can just take it in his tree
>> with
>> >> his
>> >> > own patchset. Then I'll rebase this patchset on v6.1-rc1.
>> >>
>> >> Sure.
>> >>
>> >> Jonathan, please go ahead and take the patch directly.
>> >
>> > Too late for me to take this for this cycle (I route via Greg KH
>> so
>> > need to have things
>> > in place a little bit before the merge window). If Lee doesn't
>> pick
>> > it up, I'll do an
>> > immutable branch after rc1 is out with just this patch on it, then
>> > anyone who wants
>> > it can pick it up.
>>
>> Rafael or Lee, can you take it now?
>>
>> Or is it already too late? :(
>
> I've applied this patch as 6.1-rc material, thanks!
Awesome, thanks!
-Paul
next prev parent reply other threads:[~2022-10-04 19:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:40 [PATCH v2 00/30] mfd: Remove #ifdef guards for PM functions Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 01/30] pm: Improve EXPORT_*_DEV_PM_OPS macros Paul Cercueil
2022-08-13 14:49 ` Jonathan Cameron
2022-08-23 17:47 ` Rafael J. Wysocki
2022-08-25 22:42 ` Paul Cercueil
2022-09-25 14:52 ` Jonathan Cameron
2022-09-26 12:00 ` Rafael J. Wysocki
2022-09-26 13:27 ` Paul Cercueil
2022-09-26 13:35 ` Rafael J. Wysocki
2022-10-01 17:01 ` Jonathan Cameron
2022-10-02 11:18 ` Paul Cercueil
2022-10-04 18:54 ` Rafael J. Wysocki
2022-10-04 19:12 ` Paul Cercueil [this message]
2022-08-08 17:40 ` [PATCH v2 02/30] mfd: 88pm80x: Remove #ifdef guards for PM related functions Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 03/30] mfd: aat2870: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 04/30] mfd: adp5520: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 05/30] mfd: max8925-i2c: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 06/30] mfd: mt6397-irq: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 07/30] mfd: pcf50633: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 08/30] mfd: rc5t583-irq: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 09/30] mfd: stpmic1: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 10/30] mfd: ucb1x00: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 11/30] mfd: 88pm860x: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 12/30] mfd: intel_soc_pmic: " Paul Cercueil
2022-08-23 14:17 ` Andy Shevchenko
2022-08-08 17:40 ` [PATCH v2 13/30] mfd: mcp-sa11x0: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 14/30] mfd: sec: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 15/30] mfd: sm501: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 16/30] mfd: tc6387xb: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 17/30] mfd: tps6586x: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 18/30] mfd: wm8994: " Paul Cercueil
2022-08-22 9:43 ` Charles Keepax
2022-08-08 17:40 ` [PATCH v2 19/30] mfd: max77620: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 20/30] mfd: t7l66xb: " Paul Cercueil
2022-08-08 17:40 ` [PATCH v2 21/30] mfd: arizona: " Paul Cercueil
2022-08-22 9:44 ` Charles Keepax
2022-08-08 17:40 ` [PATCH v2 22/30] mfd: max14577: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 23/30] mfd: max77686: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 24/30] mfd: motorola-cpcap: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 25/30] mfd: sprd-sc27xx: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 26/30] mfd: stmfx: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 27/30] mfd: stmpe: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 28/30] mfd: tc3589x: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 29/30] mfd: tc6393xb: " Paul Cercueil
2022-08-08 17:41 ` [PATCH v2 30/30] mfd: intel-lpss: " Paul Cercueil
2022-08-13 14:50 ` [PATCH v2 00/30] mfd: Remove #ifdef guards for PM functions Jonathan Cameron
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=KDT8JR.QPETUDEUEUK4@crapouillou.net \
--to=paul@crapouillou.net \
--cc=jic23@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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
all inboxes | Powered by JetHome®