Hi!
> > I think the correct x86 solution would be to introduce a real dummy
> > option for the menus, and imply CONFIG_PM if APM or swsusp (the two
> > options that seem to actually need CONFIG_PM code) is enabled.
>
> I can buy that. There are actually three levels of power management that
> we handle:
>
> - System Power Management (swsusp, CONFIG_ACPI_SLEEP)
> - Device Power Management (kernel/pm.c, future driver model support)
> - CPU Power Management (cpufreq)
>
> SPM implies that DPM will be enabled, but both DPM and CPM can exist
> without SPM, and independently of each other. All of them would
> essentially fall under CONFIG_PM..
>
> Would you willing to whip up a patch for the Kconfig entries?
We have enough trouble making sure *current* PM code runs with all possible
config combinations; I do not think we want more PM options for now.
-- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...- 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 Aug 07 2003 - 22:00:35 EST