From: Greg KH <gregkh@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
oneukum@suse.de, Linux-pm mailing list <linux-pm@lists.osdl.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [PATCH]switching off autosuspend through sysfs
Date: Wed, 24 Jan 2007 17:15:24 -0800 [thread overview]
Message-ID: <20070125011523.GA4542@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0701241145140.4368-100000@iolanthe.rowland.org>
On Wed, Jan 24, 2007 at 11:51:17AM -0500, Alan Stern wrote:
> On Tue, 23 Jan 2007, Greg KH wrote:
>
> > On Tue, Jan 23, 2007 at 04:22:43PM -0800, David Brownell wrote:
> > > > > > static struct attribute *dev_attrs[] = {
> > > > > > + /* power management attributes */
> > > > > > + &dev_attr_autosuspend.attr,
> > > > >
> > > > > Belongs in /sys/devices/.../power/... then, right?
> > > >
> > > > No, I thought we want to drop that power/ directory.
> > >
> > > Dropping that directory hasn't AFAIK ever been discussed.
> > > If it were to be dropped, where would the per-device wakeup
> > > flags live?
> >
> > I don't know, it just really annoys me to see that power directory there
> > with no use for it for a lot of devices :)
>
> Would it help to add a flag somewhere in struct device (or struct
> dev_pm_info) for indicating that the device is not cognizant of PM? For
> instance, all those USB endpoint pseudo-devices we create -- it's a waste
> of time to try doing power management on them and it generates a bunch of
> useless and distracting warning messages in the system log.
Yes. In fact we should just make it a "has pm" type flag, as the
majority of devices do not.
So, what kind of devices do support these files? I can think of:
PCI
USB
and that's it right now. Do platform devices really use those files?
thanks,
greg k-h
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2007-01-25 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070124003221.GA3755@suse.de>
2007-01-24 16:51 ` [linux-usb-devel] [PATCH]switching off autosuspend through sysfs Alan Stern
2007-01-25 1:15 ` Greg KH [this message]
2007-01-25 1:28 ` [linux-pm] " Greg KH
2007-01-25 16:03 ` Alan Stern
2007-01-25 2:15 ` David Brownell
2007-01-25 11:13 ` [linux-pm] " David Brownell
2007-01-25 16:09 ` [linux-usb-devel] " Alan Stern
2007-01-26 14:27 ` Oliver Neukum
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=20070125011523.GA4542@suse.de \
--to=gregkh@suse.de \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oneukum@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.