From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Greg KH <greg@kroah.com>
Cc: len.brown@intel.com, linux-pm@lists.linux-foundation.org, pavel@suse.cz
Subject: Re: [RFC Add in_use attribute] Let the driver know if it's in use
Date: Tue, 21 Apr 2009 20:33:01 +0200 [thread overview]
Message-ID: <200904212033.02035.rjw@sisk.pl> (raw)
In-Reply-To: <20090420221518.GA28499@kroah.com>
On Tuesday 21 April 2009, Greg KH wrote:
>
> I seem to not have seen the original post about this, thanks Alan for
> adding me to the cc:
>
> On Mon, Apr 20, 2009 at 06:11:18PM -0400, Alan Stern wrote:
> > On Mon, 20 Apr 2009, Rafael J. Wysocki wrote:
> >
> > > On Thursday 16 April 2009, Michael Trimarchi wrote:
> > > > Drivers on embedded systems would be smart enough
> > > > to know that some of the devices should remain powered up, because
> > > > they could still be useful even when the CPU wasn't running.
> > > > The patch add the in_use attribute, that it can be used by the
> > > > the drivers to avoid power down during suspend.
>
> I'm confused, why would a driver not know if it was in use or not?
> Actually, how would it not know already by virtue of what is happening
> within it (io in flight, buttons being pushed, dma streaming, etc.)?
>
> > > OK, so the idea is that in_use will be set by the user space for devices that
> > > shouldn't be suspended. Is this correct?
>
> So userspace knows better than the kernel as to if a specific driver is
> being used at the moment? Why is this so?
The name of the flag is not the best one. :-)
The flag is supposed to mean "don't suspend this device during system-wide
suspend, because it's being used for something you may be unaware of".
AFAICS.
Best,
Rafael
next prev parent reply other threads:[~2009-04-21 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 13:13 [RFC Add in_use attribute] Let the driver know if it's in use Michael Trimarchi
2009-04-20 9:09 ` Michael Trimarchi
2009-04-20 21:54 ` Rafael J. Wysocki
2009-04-20 22:11 ` Alan Stern
2009-04-20 22:15 ` Greg KH
2009-04-21 18:33 ` Rafael J. Wysocki [this message]
2009-04-21 21:55 ` Greg KH
2009-04-21 5:17 ` Michael Trimarchi
2009-04-21 18:30 ` Rafael J. Wysocki
2009-04-20 22:45 ` Greg KH
2009-04-21 5:08 ` Michael Trimarchi
2009-04-21 6:17 ` Greg KH
2009-04-21 6:43 ` Michael Trimarchi
2009-04-21 21:56 ` Greg KH
2009-04-23 8:47 ` Michael Trimarchi
2009-04-23 14:59 ` Rafael J. Wysocki
2009-04-23 16:49 ` Michael Trimarchi
2009-04-23 21:41 ` Rafael J. Wysocki
2009-04-21 5:01 ` Michael Trimarchi
2009-04-21 18:46 ` Rafael J. Wysocki
2009-04-23 6:01 ` Michael Trimarchi
2009-04-23 6:11 ` Michael Trimarchi
2009-04-23 14:56 ` 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=200904212033.02035.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
/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