From: ulf.hansson@linaro.org (Ulf Hansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/8] PM / Runtime: Fetch runtime PM callbacks using a macro
Date: Thu, 27 Feb 2014 22:13:51 +0100 [thread overview]
Message-ID: <CAPDyKFq4X3G1zZay0XG2g-djEvyRdf9s47GDSC5htXZ7c-LdRQ@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1402271120280.888-100000@iolanthe.rowland.org>
On 27 February 2014 17:22, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 27 Feb 2014, Ulf Hansson wrote:
>
>> > A reasonable compromise would be to define the macro, and then use it
>> > in those three new functions (and nowhere else).
>>
>> Okay, let me send a v3 that tries this approach then.
>>
>> >
>> > The existing rpm_idle, rpm_suspend, and rpm_resume routines should then
>> > be changed to use the new functions. And of course, the new functions
>> > could be called directly by subsystems or PM domains.
>>
>> Not sure we should export these functions as a part of this patchset.
>> Would it not be preferred, to first see if there are any that needs
>> it?
>
> I don't understand. V2 of the patchset exports
> pm_runtime_force_suspend and pm_runtime_force_resume. Why wouldn't you
> want to export them in V3?
There are some confusion here. :-) pm_runtime_force_suspend|resume()
surely need to be exported, but that's "patch v2 2/8".
I think we were debating whether this patch "patch v2 1/8" should use
a macro to walk the ladder to fetch the runtime PM callback - or if we
should implement a three c-functions to handle it. I prefer to keep
this patch as is, thus using the macro.
Kind regards
Ulf Hansson
>
> Alan Stern
>
next prev parent reply other threads:[~2014-02-27 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 10:22 [PATCH V2 1/8] PM / Runtime: Fetch runtime PM callbacks using a macro Ulf Hansson
2014-02-26 23:00 ` Kevin Hilman
2014-02-26 23:13 ` Ulf Hansson
2014-02-27 15:04 ` Alan Stern
2014-02-27 15:26 ` Ulf Hansson
2014-02-27 16:22 ` Alan Stern
2014-02-27 21:13 ` Ulf Hansson [this message]
2014-02-27 21:25 ` Alan Stern
2014-02-27 22:36 ` Ulf Hansson
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=CAPDyKFq4X3G1zZay0XG2g-djEvyRdf9s47GDSC5htXZ7c-LdRQ@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).