Am Donnerstag, 5. Juli 2007 schrieb Alan Stern: > On Thu, 5 Jul 2007, Oliver Neukum wrote: > > > Am Donnerstag, 5. Juli 2007 schrieb Alan Stern: > > > Allow me to rephrase. You seem to be saying that /sys/.../power/wakeup > > > should be able to hold four different values: > > > > > > 1. always disabled > > > 2. always enabled > > > 3. enabled at runtime but not during system sleep > > > 4. enabled during system sleep but not at runtime > > > > > > Right? With the default being 3 (except for a few things like the > > > power button). > > > > > > Or maybe there should be two attribute files: wakeup (used during > > > system sleep) and wakeup_runtime (used for runtime suspend). > > > > > > Comments from anybody else? > > > > I am not sure we ever want to do runtime suspend without remote wakeup. > > You mean the user shouldn't be able to disable remote wakeup during a > runtime suspend? But what if the user wants to put the device to sleep > with no possibility of wakeup? Then the user will have to force suspend anyway and we can use the existing attribute. Two points: 1. For hubs I don't think we should allow it 2. The important distinction is not between system wide vs. device, but between forced sleep and the "best effort" runtime suspension in style of autosuspend. The latter needs remote wakeup under control of the driver. Regards Oliver _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
