From: Russell King <rmk@arm.linux.org.uk>
To: cpufreq@zenII.linux.org.uk
Subject: [BUG] cpufreq on SMP with CPUs present but not online
Date: Mon, 17 Jan 2005 22:38:27 +0000 [thread overview]
Message-ID: <20050117223827.D31178@flint.arm.linux.org.uk> (raw)
... causes the cpufreq driver init method to be called for each CPU.
However, this causes something of a dilema on ARM/SMP - if the CPU
is not online (because we failed to bring it up via __cpu_up which
correctly returned an error), we can't read the current clock rate
settings, so we can't initialise policy->{cur,min,max} fields.
Returning an error from the cpufreq driver init method means that
cpufreq completely forgets about this particular CPU, which also
isn't desirable.
Ideas?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next reply other threads:[~2005-01-17 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 22:38 Russell King [this message]
2005-01-18 18:06 ` [BUG] cpufreq on SMP with CPUs present but not online Dominik Brodowski
2005-01-18 19:08 ` Russell King
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=20050117223827.D31178@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@zenII.linux.org.uk \
/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