[lkml]   [2003]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [linux-usb-devel] Re: OHCI problems with suspend/resume

> >>root; and resume in the reverse order. Is that behaving now?
> >
> >
> >Yes.
> Well, partially; but it's not used consistently. Could you
> (or someone) explain what the plan is? I see:
> - Three separate x86 PM "initiators": APM, ACPI, swsusp.
> (Plus ones for ARM and MIPS.)
> - Two driver registration infrastructures, the driver model
> stuff and the older pm_*() stuff.
> The pm_*() is how a handful of sound drivers and other random
> stuff register themselves -- and how PCI does it.
> I'd sure have expected PCI to only use the driver model stuff,
> and I'll hope all those users will all be phased out by the
> time that 2.6 gets near the end of its test cycle.

Ouch, PCI really should use new driver model. I have not known about
that. I'll look into it.

> The "initiators" all talk to _both_ infrastructures, but they
> don't talk to the driver model stuff in the same way. For
> example, on suspend:
> - ACPI issues a NOTIFY, which can veto the suspend;
> then SAVE_STATE, ditto; finally POWER_DOWN.
> - APM uses the pm_*() calls for a vetoable check,
> never issues SAVE_STATE, then goes POWER_DOWN.

IIRC, I had SAVE_STATE there at some point, and there was some
problem. I do not really use APM :-(.

> - While swsusp is more like ACPI except that it doesn't
> support vetoing from either NOTIFY or SAVE_STATE.

Good. I figured vetoing support is not critical. I should add it.

> That all seems more problematic to me. Seems to me that
> APM should issue SAVE_STATE (and RESTORE_STATE), and all
> three PM "initiators" should agree on vetoing.

Yes, agreed.

> All of which is a roundabout way of adding to what I
> said: the PM infrastructure USB will need to rely on
> seems like it needs polishing yet! :)

Do you need vetoing? Otherwise it should be ready, except for APM.

When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.195 / U:4.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site