Re: Solving suspend-level confusion

[David Brownell]

On Tuesday 03 August 2004 19:26, Nigel Cunningham wrote:

> > There's now some partial-tree code in CONFIG_USB_SUSPEND (for
> > developers only), but jumping from USB into the next level driver
> > (SCSI, video, etc) raises questions.
> 
> I've also done partial-tree support for suspend2 by making a new list
> (along side the active, off and off_irq lists) and simply moving devices
> I want to keep on (plus their parents) to this list prior to calling
> device_suspend. Works well for keeping alive the ide devices being used
> write the image.

What I'd need out of the PM framework would be "suspend this subtree",
and its cousin "resume this subtree".  Where the subtree starts with a
given device ... and, if it's got a driver, any abstract devices created
by that driver.  (And their children, etc.)

I'm not sure what to think about the desire of "suspend2" to prevent
a subtree from suspending.  In fact, I'm not at all sure how to even
interpret a "can't suspend" failure code... device in trouble, likely.

- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/