archive mirror
 help / color / mirror / Atom feed
From: Patrick Mochel <>
To: Tomas Szepe <>
Cc: Ducrot Bruno <>, lkml <>
Subject: Re: [TRIVIAL] sanitize power management config menus, take two
Date: Tue, 5 Aug 2003 10:47:47 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308051006060.23977-100000@cherise> (raw)
In-Reply-To: <>

> Trouble is, the same goes for ACPI -- it doesn't require that CONFIG_PM
> code be present.

I initially missed that part of your patch, and that is incorrect - Only
part of ACPI (CONFIG_ACPI_SLEEP) should depend on CONFIG_PM.

> 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? 


  parent reply	other threads:[~2003-08-05 17:43 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 [this message]
2003-08-05 17:46               ` Tomas Szepe
2003-08-06  9:20               ` Ducrot Bruno
2003-08-06 13:06               ` Pavel Machek
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0308051006060.23977-100000@cherise \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).