From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2)
Date: Fri, 5 Feb 2010 07:27:19 +0100 [thread overview]
Message-ID: <20100205062718.GA1384@ucw.cz> (raw)
In-Reply-To: <201002050008.52699.rjw@sisk.pl>
> > > + * The default for all devices is "auto", which means that devices may be
> > > + * subject to automatic power management, depending on their drivers.
> >
> > Is it wise to specify 'auto' default value for devices without runtime
> > pm?
>
> Yes, it is. It means the user space doesn't care whether or not the device is
> power managed at run-time.
Well, defaulting to 'on' for drivers when runtime pm is experimental
seems logical. and there will be such drivers...
> > > + len = cp - buf;
> > > + if (len == sizeof ctrl_auto - 1 && strncmp(buf, ctrl_auto, len) == 0)
> > > + pm_runtime_allow(dev);
> >
> > parenthesis after sizeof?
>
> This notation is used throughout this file too.
...but is inconsistent with rest of kernel.
> > Do I read it correctly that all of
> >
> > "auto"
> > "auto\n"
> > "auto\non\nIm confused"
> >
> > will switch to auto?
>
> Perhaps it would, but what exactly is the problem with that?
That apps will start depending on such broken behaviour?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-02-05 6:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 0:29 [RFC][PATCH] PM / Runtime: Add sysfs switch for disabling device run-time PM Rafael J. Wysocki
2010-01-18 16:10 ` Alan Stern
2010-01-18 22:25 ` [Update][RFC][PATCH] " Rafael J. Wysocki
2010-01-19 15:40 ` Alan Stern
2010-01-19 20:32 ` Rafael J. Wysocki
2010-01-19 23:27 ` Rafael J. Wysocki
2010-01-20 15:09 ` Alan Stern
2010-01-20 21:09 ` Rafael J. Wysocki
2010-01-20 21:37 ` Alan Stern
2010-01-20 22:17 ` Rafael J. Wysocki
2010-01-20 2:51 ` [RFC][PATCH] " Greg KH
2010-01-20 20:55 ` Rafael J. Wysocki
2010-01-20 22:50 ` Greg KH
2010-01-21 22:57 ` [PATCH 0/2] " Rafael J. Wysocki
2010-01-21 22:59 ` [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2) Rafael J. Wysocki
2010-01-22 3:02 ` Alan Stern
2010-01-22 20:56 ` Rafael J. Wysocki
2010-01-22 22:45 ` Alan Stern
2010-01-22 22:55 ` Rafael J. Wysocki
2010-01-23 3:22 ` Alan Stern
2010-01-23 12:14 ` Rafael J. Wysocki
2010-01-23 15:20 ` Alan Stern
2010-01-23 20:08 ` Rafael J. Wysocki
2010-02-04 22:46 ` Pavel Machek
2010-02-04 23:08 ` Rafael J. Wysocki
2010-02-05 6:27 ` Pavel Machek [this message]
2010-02-05 15:19 ` Alan Stern
2010-02-05 8:03 ` [linux-pm] " Nigel Cunningham
2010-01-21 23:00 ` [PATCH 2/2] PM: Document device power attributes in sysfs Rafael J. Wysocki
2010-01-24 15:56 [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2) Jesse Barnes
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=20100205062718.GA1384@ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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
Powered by JetHome