On Saturday, October 02, 2010, Alan Stern wrote: > On Fri, 1 Oct 2010, Rafael J. Wysocki wrote: ... > > At the moment it suspends when the network cable is removed from the device > > and the hack I mentioned is used during the resume after the cable has been > > reinserted (it checks if the cable is still there and schedules suspend if not). > > That does seem like a strange hack. Instead of scheduling a suspend, > why not simply do a suspend as soon as you learn that the cable has > been removed again? Is there a problem about the connection status > bouncing? I don't remember 100%, but ISTR there was a problem with that. > > If we removed the immediate idle notification after a successful resume, it > > might need to be reworked slightly. > > My suggestion was that we remove the idle notification after a failed > suspend, not the notification after a successful resume. And I said I was fine with that. Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
