From: Mark Lord <lkml@rtr.ca>
To: Adrian Bunk <bunk@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
Oliver Neukum <oneukum@suse.de>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
Date: Fri, 14 Sep 2007 09:21:08 -0400 [thread overview]
Message-ID: <46EA8AC4.3000007@rtr.ca> (raw)
In-Reply-To: <alpine.LFD.0.999.0709131709320.16478@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Fri, 14 Sep 2007, Adrian Bunk wrote:
>> E.g. when looking at the reverse dependencies of libhal, it would not be
>> funny if kernel 2.6.43 required a more recent version of HAL.
>
> Adrian, what's the point of answering your questions, WHEN YOU DON'T EVEN
> READ THE ANSWERS!
>
> So stop repeating your inane question, and instead LISTEN to what people
> are saying.
>
> There is *no* requirement what-so-ever on user space. End of story.
>
> If user-space doesn't tell devices to go to autosuspend, they just won't
> do so. But this has nothing to do with white-lists, black-lists, 2.6.43,
> or your HAL version.
>
> That black-listing was a mistake. We got over it. Now PLEASE you get over
> it too!
Adrian, please note that this is NOT the normal "suspend to ram/disk" stuff
that is being discussed / affected here. But rather something brand new
(to Linux), the automatic powerdown (well, nearly) of idle USB devices
during regular running.
Things will work just fine without chewing up gobs of memory in a futile effort
to list everything inside the kernel. Devices will plug in and work fine
(which they didn't in 2.6.23 until this stuff got reverted) the same as always.
To gain the last xx% in power savings, some userspace support may be needed,
that's all. And with the pace of new/updated USB devices coming/going these days,
userspace is really the only appropriate place for this kind of stuff.
Cheers
next prev parent reply other threads:[~2007-09-14 13:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 13:33 [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6 Greg KH
2007-09-13 14:52 ` Adrian Bunk
2007-09-13 15:20 ` Alan Stern
2007-09-13 15:40 ` Adrian Bunk
2007-09-13 16:07 ` Alan Stern
2007-09-13 16:34 ` Greg KH
2007-09-13 16:43 ` Linus Torvalds
2007-09-13 19:13 ` Alan Stern
2007-09-14 0:24 ` Matthew Dharm
2007-09-14 14:34 ` Alan Stern
2007-09-14 8:55 ` Jiri Kosina
2007-09-14 9:59 ` Greg KH
2007-09-13 19:26 ` Pete Zaitcev
2007-09-13 20:19 ` Adrian Bunk
2007-09-13 20:31 ` Alan Stern
2007-09-13 20:44 ` Linus Torvalds
2007-09-13 21:28 ` Adrian Bunk
2007-09-13 22:05 ` Adrian Bunk
2007-09-14 0:11 ` Linus Torvalds
2007-09-14 13:21 ` Mark Lord [this message]
2007-09-14 14:15 ` Adrian Bunk
2007-09-14 14:29 ` Alan Stern
2007-09-14 14:26 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 12:56 Hans de Goede
2007-09-18 10:39 Joerg Schilling
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=46EA8AC4.3000007@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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