Re: Solving suspend-level confusion

[Benjamin Herrenschmidt]

On Sun, 2004-08-08 at 08:14, David Brownell wrote:
> On Friday 06 August 2004 13:04, Pavel Machek wrote:
> 
> > > These look to me like "wrong device-level suspend state" cases.
> > 
> > Actually, suspend-to-disk has to suspend all devices *twices*. Once it
> > wants them in "D0 but DMA/interrupts stopped", and once in "D3cold but
> > I do not really care power is going to be cut anyway". I do not think
> > this can be expressed with PCI states.
> 
> How are those different from "PCI_D1" then later "PCI_D3hot"?

D1 is a real HW state, we don't really need to enter it at all. On some
chip, suspending to D1 require some mess that we don't need here. We
just need to block the driver.

> I'd understood that loss of VAUX was always possible, so robust
> drivers always had to handle resume  from PCI_D3cold.

When they can ....

Ben.


-
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/