From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: cpufreq@lists.linux.org.uk
Subject: cpufreq issue
Date: Tue, 29 Mar 2005 12:01:11 +1000 [thread overview]
Message-ID: <1112061671.5768.3.camel@gaston> (raw)
Hi !
I'm trying to solve a long standing cpufreq issue on pmac. That includes
adding a suspend() callback in addition to the restore one, but that
also includes the need for me to switch to high speed on suspend. The
problem is that at this point, IRQs are disabled, which mean that
calling the notifier will BUG()... However, I must trigger the jiffies
adjustement...
What do you suggest ? Maybe I could have the core cpufreq suspend()
routine do a bit like resume(), and so right after it calls my driver
suspend(), compare the frequency with get() (if any) and update the
jiffies ? Or what ? The problem is that I need to make sure the machine
is in high speed before sleep for various HW reasons, and I must make
sure the jiffies are recalculated properly since some low level stuff
will rely on udelay() beeing "good enough" before cpufreq gets a chance
to resume and thus "fixup" the loops_per_jiffies ...
Ben.
reply other threads:[~2005-03-29 2:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1112061671.5768.3.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux@dominikbrodowski.net \
/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