Hi! > > > The last notion that made sense to me was having > > > "frozen" just be another suspend state ... one that > > > places even fewer constraints than system-S1 does. > > > > Don't confuse driver states with device states. FREEZE is primarily a > > driver notion whereas SUSPEND is definitely a device state (although > > it implies FREEZE, of course). > > But see the example I gave above, with root hubs. There > are three driver model devices: hub interface, hub device, > and controller. All have drivers. FREEZE and SUSPEND would > of necessity apply to each device, and thus to each driver! > > And there don't seem to be any generally useful behavioral > distinctions between those states. That's maybe most visible > for the devices that don't directly map to hardware ... like > the interface devices in USB, or network class devices. Doing SUSPEND when you are asked to do FREEZE is always correct, but it may be unneccessarily slow. If you want USB to stay simple, slowness may not matter to you. It can always be fixed later. For devices like disk it does matter, you do not want to spindown for FREEZE. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
