From: Russell King <rmk@arm.linux.org.uk>
To: Dave Jones <davej@redhat.com>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq on ARM broken
Date: Wed, 2 Jun 2004 22:36:19 +0100 [thread overview]
Message-ID: <20040602223619.C9322@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040602122153.GB8781@dominikbrodowski.de>; from linux@dominikbrodowski.de on Wed, Jun 02, 2004 at 02:21:53PM +0200
On Wed, Jun 02, 2004 at 02:21:53PM +0200, Dominik Brodowski wrote:
> On Tue, Jun 01, 2004 at 06:11:34PM +0100, Dave Jones wrote:
> > Thoughts ?
> > I've forgotten why we introduced this flag, it appears that this
> > would be the first thing in the tree to actually use it,
> > which makes me sceptical.
>
> This flag was introduced when I added the "fail if no proper CPU found"
> feature, which is helpful for the ACPI P-States driver and some other x86
> drivers which only check whether they can run on _any_ CPU in the
> cpu-specific initialization call. To assert backwards-compatibility, this
> flag avoids "automatic unregistration" -- I wasn't aware some drivers do
> need this backwards compatibility, but obviously ARM needs it. So Russell's
> patch looks to be what's needed, from my perspective.
It isn't back-compat. It's caused by a side effect of how the order of
initialisation.
--
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
prev parent reply other threads:[~2004-06-02 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 16:01 cpufreq on ARM broken Russell King
2004-06-01 17:11 ` Dave Jones
2004-06-02 12:21 ` Dominik Brodowski
2004-06-02 12:59 ` Dave Jones
2004-06-02 13:08 ` Dominik Brodowski
2004-06-02 21:36 ` Russell King [this message]
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=20040602223619.C9322@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
/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