Hi, On Wednesday, 28 of September 2005 15:04, Pavel Machek wrote: > Hi! > > > I guess there are three possible solutions: > > 1) Leave things as they are and say it is the user's problem if they > > make the state inconsistent. > > 2) Keep knowledge of the device states across the atomic restore and use > > that information in deciding what to do in device resume/powerup. > > 3) Make device drivers handle the situation properly without knowledge > > of what state the hardware is really in (or check the real state - where > > possible - and rely on that in deciding what to do). > > > > 2 seems to me to make for the most reliable solution. > > I actually like 3 most -- it does not need core changes. IMO if the driver is a module it should not make any assumptions on the state of the device when its resume routine is called. Instead, it should assume the device can be in an arbitrary state and proceed in the safest way possible. Which is 3. Greetings, Rafael
