From: Dave Jones <davej@redhat.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreq_driver->resume
Date: Tue, 2 Sep 2003 12:08:26 +0100 [thread overview]
Message-ID: <20030902110826.GA30038@redhat.com> (raw)
In-Reply-To: <20030902083227.GB3958@brodo.de>
On Tue, Sep 02, 2003 at 10:32:27AM +0200, Dominik Brodowski wrote:
> +cpufreq_driver.resume - A pointer to a per-CPU resume function
> + which is called with interrupts disabled
> + and _before_ the pre-suspend frequency
> + and/or policy is restored by a call to
> + ->target or ->setpolicy.
> +
What advantage is there to doing things this way over just
setting the speed to the last known value before we suspended ?
(though some drivers may need fixing, as they shortcut the
'trying to set to current speed' thing with a return so we
don't actually poke anything.)
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-09-02 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 8:32 [RFC] cpufreq_driver->resume Dominik Brodowski
2003-09-02 11:08 ` Dave Jones [this message]
2003-09-02 13:41 ` Dominik Brodowski
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=20030902110826.GA30038@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@brodo.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox