Hi Matthew, > The bcm5974 code takes a USB autosuspend reference on device open and > releases it on device close. This means that the hardware won't sleep when > anything holds it open. This is sensible for input devices that don't > support remote wakeups on normal use (like most mice), but this hardware > trigger wakeups on touch and so can suspend transparently to the user. Doing > so allows the USB host controller to sleep when the machine is idle, giving > measurable power savings. > > Signed-off-by: Matthew Garrett <mjg@xxxxxxxxxx> > --- > > Correctly flag needs_remote_wake. With this patch, autosuspend seems to work correctly after boot, while keeping a device file open. When all device files are closed, the looping suspend/resume behavior is still there. Moreover, when coming back from a user suspend, rpm_suspend fails with EBUSY on my machine, and the device will not autosuspend thereafter. IOW, getting closer, but still no cigar, sorry. Cheers, Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
