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  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:	Sun, 1 Mar 2009 23:56:47 +0100
From:	Pavel Machek <>
To:	Arve Hj?nnev?g <>
Cc:	"Rafael J. Wysocki" <>,
	Alan Stern <>,
	"Woodruff, Richard" <>,
	Arjan van de Ven <>,
	Kyle Moffett <>,
	Oliver Neukum <>,
	Benjamin Herrenschmidt <>,
	pm list <>,
	LKML <>,
	Nigel Cunningham <>,
	Matthew Garrett <>,
	mark gross <>,
	Uli Luckas <>,
	Igor Stoppa <>,
	Brian Swetland <>,
	Len Brown <>
Subject: Re: [RFD] Automatic suspend


> >> > Phase 3: Probably explicit control left to open/close.
> >>
> >> While that's generally a good idea, it's important to recognize that
> >> some devices should be runtime-suspended even while they are open.
> >
> > From the kernel side, yes (and that should be transparent to the user space
> > having them open).  By the user space, no.
> Allowing user space to suspend input devices while they are still open
> is useful. The user-space code that reads from the input devices does
> not need to know if the device is suspended or not, and the kernel
> cannot auto suspend input devices based on inactivity.

Actually, I'd like you to fix your userspace and close input devices
when it does not need them. Given the way you control the platform it
should not be that hard. I do not see why we'd want to invent new
interface for "uhuh, I have opened the keyboard but I am not really
interested in keys being pressed".
(cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists