From: Pavel Machek <pavel@ucw.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Tomas Szepe <szepe@pinerecords.com>,
Ducrot Bruno <poup@poupinou.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL] sanitize power management config menus, take two
Date: Wed, 6 Aug 2003 15:06:53 +0200 [thread overview]
Message-ID: <20030806130652.GA6914@openzaurus.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0308051006060.23977-100000@cherise>
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...
next prev parent reply other threads:[~2003-08-06 20:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 7:26 [TRIVIAL] sanitize power management config menus, take two Tomas Szepe
2003-08-05 16:11 ` Ducrot Bruno
2003-08-05 16:15 ` Tomas Szepe
2003-08-05 16:24 ` Ducrot Bruno
2003-08-05 16:26 ` Tomas Szepe
2003-08-05 16:36 ` Tomas Szepe
2003-08-05 16:48 ` Patrick Mochel
2003-08-05 16:51 ` Tomas Szepe
2003-08-05 17:01 ` Tomas Szepe
2003-08-05 17:47 ` Patrick Mochel
2003-08-05 17:46 ` Tomas Szepe
2003-08-06 9:20 ` Ducrot Bruno
2003-08-06 13:06 ` Pavel Machek [this message]
2003-08-05 16:55 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 7:43 John Bradford
2003-07-27 12:18 Tomas Szepe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030806130652.GA6914@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=poup@poupinou.org \
--cc=szepe@pinerecords.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.