All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.6.7-mm1] perfctr ppc32 update
Date: Tue, 22 Jun 2004 16:19:55 -0500	[thread overview]
Message-ID: <1087939194.1839.13.camel@gaston> (raw)
In-Reply-To: <16600.39256.669322.177553@alkaid.it.uu.se>


> So what you're saying is that PLL_CFG may not reflect the true
> relationship between the TB frequency and the core frequency?

Right.

> That shouldn't be a problem as long as there's _some_ in-kernel
> interface for finding that out. If querying OF isn't the correct
> approach, then what is?

What do you need exactly ? The TB one or the core one ? the core
I suppose ? Well, we should probably define an ppc_get_cpu_core_frequency
or something like that that uses the cpufreq callback like the pmac code
when cpufreq is enabled or default to the old parsing when not. Look at
the pmac code. You may also want to install a cpufreq notifier callback
to be informed of core frequency changes.

Ben.


  reply	other threads:[~2004-06-22 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 20:14 [PATCH][2.6.7-mm1] perfctr ppc32 update Mikael Pettersson
2004-06-22 18:17 ` Benjamin Herrenschmidt
2004-06-22 20:09   ` Mikael Pettersson
2004-06-22 20:21     ` Benjamin Herrenschmidt
2004-06-22 20:40       ` Mikael Pettersson
2004-06-22 21:19         ` Benjamin Herrenschmidt [this message]
2004-06-22 22:18           ` Mikael Pettersson
2004-06-22 22:14             ` Benjamin Herrenschmidt

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=1087939194.1839.13.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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.