Hi!
> 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.
>
>
> 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.
>
> - While swsusp is more like ACPI except that it doesn't
> support vetoing from either NOTIFY or SAVE_STATE.
Where does acpi call pm_*()? It seems like it does not and it seems
like a bug to me.
Pavel
-- 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:49 EST