From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
To: Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
pm list
<linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [linux-pm] [PATCH] i2c: Hook up runtime PM support
Date: Fri, 5 Feb 2010 23:09:13 +0100 [thread overview]
Message-ID: <201002052309.13966.rjw@sisk.pl> (raw)
In-Reply-To: <20100205103915.GA2600-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Friday 05 February 2010, you wrote:
> On Thu, Feb 04, 2010 at 10:57:27PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday 03 February 2010, Mark Brown wrote:
> > > Allow I2C drivers to make use of the runtime PM framework by adding
> > > bus implementations of the runtime PM operations. These simply
> > > immediately suspend when the device is idle.
>
> > Perhaps it would be a good idea to give the driver a chance to veto
> > the suspend by calling its _idle callback? We do that for PCI and turns out to
> > be quite useful.
>
> Hrm, I guess. It seems an odd thing to want to use - for a bus like I2C
> there's nothing other than the driver involved so the request that is
> being vetoed will have been initiated by the driver which seems wrong.
Not really. _idle is also called automatically by the runtime PM core after
_resume in case the device may be suspended again. Your _idle has to handle
this case as well and that's when the driver may want to veto the suspend.
> Out of interest do you have any pointers to drivers using this (my greps
> aren't turning anything up in -next)?
There aren't any in -next, because I'm waiting for the base PCI runtime PM
code to settle down. I have two in my private queue at the moment , for r8169
and e1000e (I posted some older versions of them some time ago, but they
wouldn't fit the current framework too well, which is the basic reason I'm
sitting on them, so that I don't have to post too many updates :-)).
I can send them to you privately, if needed.
Rafael
next prev parent reply other threads:[~2010-02-05 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 13:22 [PATCH] i2c: Hook up runtime PM support Mark Brown
[not found] ` <1265203367-21344-1-git-send-email-broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2010-02-04 21:57 ` Rafael J. Wysocki
[not found] ` <201002042257.27145.rjw-KKrjLPT3xs0@public.gmane.org>
2010-02-05 10:39 ` [linux-pm] " Mark Brown
[not found] ` <20100205103915.GA2600-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2010-02-05 22:09 ` Rafael J. Wysocki [this message]
[not found] ` <201002052309.13966.rjw-KKrjLPT3xs0@public.gmane.org>
2010-02-05 23:17 ` Mark Brown
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=201002052309.13966.rjw@sisk.pl \
--to=rjw-kkrjlpt3xs0@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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).