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:	Thu, 5 Oct 2006 12:21:45 -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:

> > > > If you are talking runtime suspend, you should probably just wake the
> > > > device up on first access.
> > > 
> > > Do you really think a device driver should override an explicitely
> > > selected power state?
> > 
> > (So we are talking runtime suspend?)
> 
> Yes. Otherwise the patch would have been ready two days ago.
> But if I am implenting this, I'll do a full implementation.
> 
> > No, I do not know what the right interface is. I started to suspect
> > that drivers should suspend/resume devices automatically, without
> > userland help. Maybe having autosuspend_timeout in sysfs is enough.
> 
> If you do this at kernel level, you'll screw up any demon implementing
> a power policy to stay within the budget.

Currently we don't have any userspace APIs for such a daemon to use.  The 
only existing API is deprecated and will go away soon.

Current thinking is that a driver will suspend its device whenever the 
device isn't in use.  With usblp, that would be whenever the device file 
isn't open.  See the example code in usb-skeleton.c.

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