Hi! > Finally, I'm not sure if I like the current "*probe", "*remove", "*suspend", > and "*resume" for runtime power management. I think it may be better to do > something like the following: > > *attach - allocates data structures, creates sysfs entries, prepares driver > to handle the hardware. > > *start - Sets up device resources and configures the hardware. > (mostly physical) > > *open - engages the hardware, and allows the class to use it. > (logical and physical) > > *close - disengages the hardware, and stops access > (logical and physical) > > *stop - disables the hardware at a physical level > (mostly physical) > > *detach - tears down the driver and releases it from the "struct device" > > *power - A function that saves and restores states and transitions power > - It could take the current state and the new state as arguments. And rewrite whole kernel? (Its mostly drivers, right?) I don't think so. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
