From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 02/04] Driver Core: Add idle and wakeup functions
Date: Fri, 29 May 2009 05:10:53 +0000 [thread overview]
Message-ID: <aec7e5c30905282210h23f0edc0vad4e29dd52c2e99c@mail.gmail.com> (raw)
In-Reply-To: <20090527100642.29671.52231.sendpatchset@rx1.opensource.se>
2009/5/29 Rafael J. Wysocki <rjw@sisk.pl>:
> On Wednesday 27 May 2009, Magnus Damm wrote:
>> From: Magnus Damm <damm@igel.co.jp>
>>
>> Add platform_device_idle() and platform_device_wakeup()
>> and allow architectures to implement their own versions
>> of these if CONFIG_HAVE_PLATFORM_IDLE_WAKEUP is set.
>>
>> Signed-off-by: Magnus Damm <damm@igel.co.jp>
>> ---
>>
>> Yes, this needs documentation. See [00/04] for now.
>>
>> arch/Kconfig | 3 +++
>> include/linux/platform_device.h | 8 ++++++++
>> 2 files changed, 11 insertions(+)
>>
>> --- 0002/arch/Kconfig
>> +++ work/arch/Kconfig 2009-05-26 12:31:06.000000000 +0900
>> @@ -115,3 +115,6 @@ config HAVE_DEFAULT_NO_SPIN_MUTEXES
>>
>> config HAVE_PLATFORM_DEVICE_ARCHDATA
>> bool
>> +
>> +config HAVE_PLATFORM_DEVICE_IDLE_WAKEUP
>
> Again, I'm not sure if the new CONFIG_ option is really necessary.
At least it could be combined into a single option for platform device
runtime pm. So no need to have separate kconfig options for [02/04]
and [03/04].
We could also drop the #ifdef stuff and go for weak symbols that can
be overriden by architecture code.
I'm open to suggestions. =)
/ magnus
next prev parent reply other threads:[~2009-05-29 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 10:06 [PATCH 02/04] Driver Core: Add idle and wakeup functions Magnus Damm
2009-05-28 21:29 ` Rafael J. Wysocki
2009-05-29 5:10 ` Magnus Damm [this message]
2009-06-03 9:05 ` Rafael J. Wysocki
2009-06-05 3:26 ` Magnus Damm
2009-06-05 20:42 ` Rafael J. Wysocki
2009-06-09 4:22 ` Magnus Damm
2009-06-09 23:41 ` Rafael J. Wysocki
2009-06-10 6:03 ` Magnus Damm
2009-06-10 8:19 ` 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=aec7e5c30905282210h23f0edc0vad4e29dd52c2e99c@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.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