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]
Message-ID: <Pine.LNX.4.44L0.0610051732190.7346-100000@iolanthe.rowland.org>
Date:	Thu, 5 Oct 2006 17:45:25 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Oliver Neukum <oliver@...kum.org>
cc:	Pavel Machek <pavel@....cz>, <linux-kernel@...r.kernel.org>,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] error to be returned while suspended

On Thu, 5 Oct 2006, Oliver Neukum wrote:

> I have a few observations, but no solution either:
> - if root tells a device to suspend, it shall do so

Probably everyone will agree on that.

> - the issues of manual & automatic suspend and remote wakeup are orthogonal

Except for the fact that remote wakeup kicks in only when a device is 
suspended.

> - there should be a common API for all devices

It would be nice, wouldn't it?  But we _already_ have several vastly
different power-management APIs.  Consider for example DPMI and IDE 
spindown.

> - there's no direct connection between power save and open()

Why shouldn't a device always be put into a power-saving mode whenever it 
isn't open?  Agreed, you might want to reduce its power usage at times 
even when it is open...

> The question when a device is in use is far from trivial.

Yes.  It has to be decided by each individual driver.  For simple 
character-oriented devices, "open" is a good first start.

Alan Stern

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ