On Wed, Feb 09, 2011 at 11:00:17AM -0800, Frank Rowand wrote: > and my understanding of this proposal was a goal to remove the ability > to have CONFIG_PM disabled, which results in increased memory usage > for some configurations. Not really, the goal was to simplify the PM config options to ones that are actually useful and cut down on the number of silly combinations that the randconfigs turn up. CONFIG_PM is there mostly for historical reasons, it doesn't really mean much by itself except as a gate to other options. This comes from the fact that the options exposed and the use of them doesn't really reflect the kernel power management infrastructure any more. The PM options at Kconfig level are really SUSPEND, HIBERNATION and PM_RUNTIME but for historical reasons the idoms are all based on the root PM option. This gets fiddly and confusing as you move over build coverage. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
