From: "Eugeny S. Mints" <eugeny.mints@gmail.com>
To: pm list <linux-pm@lists.osdl.org>
Subject: [RFC] CPUFreq PowerOP integration, Issues/TODO 3/3
Date: Thu, 24 Aug 2006 05:38:57 +0400 [thread overview]
Message-ID: <44ED0331.2030005@gmail.com> (raw)
- speedstep-centrino.c and speedstep-centrino-pm_core.c are no longer relevant
to CPUFreq - need to be moved out cpufreq folder
- drivers/acpi/processor_perflib.c: needs cleanup. Now it is used by PM Core
but is compiled under CONFIG_CPU_FREQ and containd CPUFreq dependent code
- cpufreq.c code needs fixing to handle creation of operatin points at
arbitrary moment ( to function properly on empty points list). For the time
being assumed initialization order is: acpi, pm core, powerop, points
registration, cpufreq core
- cpufreq statistics is broken
- hotplug/sysdev_driver needs investigation
- pm core needs hotplug support
- expample of dependent operating point registration module
- is any functionality affected by removing flags export from legacy cpufreq
driver
- suspend/resume
next reply other threads:[~2006-08-24 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 1:38 Eugeny S. Mints [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 14:52 [RFC] CPUFreq PowerOP integration, Issues/TODO 3/3 Eugeny S. Mints
2006-09-14 14:52 ` Eugeny S. Mints
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=44ED0331.2030005@gmail.com \
--to=eugeny.mints@gmail.com \
--cc=linux-pm@lists.osdl.org \
/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.