Re: Totally broken PCI PM calls

[David Brownell <david-b@pacbell.net>]

On Sunday 10 October 2004 8:42 pm, Paul Mackerras wrote:
> 
> The USB drivers aren't a good example, they are currently quite broken
> as far as suspend/resume is concerned.  They used to work just fine
> but got broken some time in the last few months.

It would have been interesting to have seen some problem report
on linux-usb-devel.  Which USB drivers, by the way?  There have
to be at least a hundred of them.

I can say that USB suspend/resume works much better now on
some x86 hardware, especially with patches in Greg's bk-usb tree;
at the level of "those never worked on 2.6 before!"  There are still
several PMcore problems getting in the way though, and I'd not
be surprised if your "used to work" translated as "somehow a
bunch of bugs canceled each other out on PPC" ...


> Maybe the real problem is that we are trying to use the device suspend
> functions for suspend-to-disk, when we don't really want to change the
> device's power state at all.

I've made that point too.  STD is logically a few steps:  quiesce system,
write image to swap, change power state.  The ACPI spec talks about
that as keeping the system in a G1/S4 powered state, but "swusp"
doesn't use that ... it does a full power-off.   And of course, full power-off
means that the BIOS probably mucks with the USB hardware, so it's
not a real resume any more.

- Dave