On Thu, 5 Jul 2007, Oliver Neukum wrote: > > > 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 Why not? > 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. The existing USB code already takes this into account. For "best effort" runtime autosuspend, if the driver wants remote wakeup capability and the user has disabled it (or the device doesn't provide it) then the autosuspend will fail. However "forced" runtime suspension will succeed regardless of whether wakeup is enabled. Alan Stern _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
