linux-kernel - Re: [linux-usb-devel] error to be returned while suspended

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Oct 2006 13:27:42 +0200
From:	Pavel Machek <pavel@....cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	linux-usb-devel@...ts.sourceforge.net,
	David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [linux-usb-devel] error to be returned while suspended

On Fri 2006-10-06 09:04:51, Oliver Neukum wrote:
> Am Freitag, 6. Oktober 2006 04:47 schrieb David Brownell:
> > On Thursday 05 October 2006 2:25 pm, Oliver Neukum wrote:
> > 
> > > - the issues of manual & automatic suspend and remote wakeup are orthogonal
> > > - there should be a common API for all devices
> > 
> > AFAIK there is no demonstrated need for an API to suspend
> > individual devices.  Of course there's the question of who
> > would _use_ such a thing (some unspecified component, worth
> > designing one first), but drivers can use internal runtime
> > suspend mechanisms to be in low power modes and hide that
> > fact from the rest of the system.  That is, activate on
> > demand, suspend when idle.
> 
> I doubt that a lot. Eg. Again, if I close the lid I may want my USB
> network cards be suspended or not and that decision might change several
> times a day. It's a policy decision in many cases. And I'd not be
> happy

If you want your usb network card suspended... there's perfectly fine
interface to do that. It is called "ifconfig usbeth0 down".

> with being required to down the interfaces to do so. Suspension should
> be as transparent as possible.

What you want is fairly hard to implement in kernel, and it is not
clear if it is kernel job after all. "Transparent" is nice, but
"simple kernel code" is nice, too.

If you have very simple&easy&nice&transparent kernel code that can do
what you want, fine; but maybe we want to trade "transparent" for
"KISS".

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/