Hi! > > 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. > > That's what it should do when resuming from disk. > > But that's not what it should do when it's being resumed just after the > memory image was created, in order to write out the image. In this case > the device is known to be in FREEZE, not SUSPEND, and to save time we > would like the driver not to go through a full resume procedure. Do you have any driver which can save some significant ammount of time that way? Pavel -- if you have sharp zaurus hardware you don't need... you know my address
