> +The > +.Fn config_deactivate > +function is called by the parent to change the child device's operational > state > +by calling the driver's activate function with a > +.Fa flags > +argument describing the targeted operational state: > +.Bd -literal > +#define DVACT_DEACTIVATE 1 /* deactivate the device */ > +#define DVACT_QUIESCE 2 /* warn the device about > suspend */ > +#define DVACT_SUSPEND 3 /* suspend the device */ > +#define DVACT_RESUME 4 /* resume the device */ > +#define DVACT_WAKEUP 5 /* tell device to recover after > resume */ > +#define DVACT_POWERDOWN 6 /* power device down */ > +.Ed
That is not right. config_deactivate always calls with DVACT_DEACTIVATE. The other actions are layered on top, and occur during suspend/resume situations. It is an unfortunate mix. These days very few drivers call this, so I unsure if it should be documented. Anyone who needs to use this is in the code up to their neck.
