From: Mikael Pettersson <mikpe@csd.uu.se>
To: Frank Rowand <frowand@mvista.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH 2/5] ppc RT: ppc_cpu_khz.patch
Date: Tue, 8 Mar 2005 10:56:22 +0100 [thread overview]
Message-ID: <16941.30406.381804.166260@alkaid.it.uu.se> (raw)
In-Reply-To: <200503072148.j27Lm8Hu006320@localhost.localdomain>
Frank Rowand writes:
> Source: MontaVista Software, Inc.
> Signed-off-by: Frank Rowand <frowand@mvista.com>
>
> Index: linux-2.6.10/arch/ppc/platforms/prpmc800.c
> ===================================================================
> --- linux-2.6.10.orig/arch/ppc/platforms/prpmc800.c
> +++ linux-2.6.10/arch/ppc/platforms/prpmc800.c
> @@ -331,6 +331,7 @@ static void __init prpmc800_calibrate_de
> tb_ticks_per_second = 100000000 / 4;
> tb_ticks_per_jiffy = tb_ticks_per_second / HZ;
> tb_to_us = mulhwu_scale_factor(tb_ticks_per_second, 1000000);
> + cpu_khz = tb_ticks_per_second / 1000;
> return;
> }
>
> @@ -371,6 +372,7 @@ static void __init prpmc800_calibrate_de
> tb_ticks_per_second = (tbl_end - tbl_start) * 2;
> tb_ticks_per_jiffy = tb_ticks_per_second / HZ;
> tb_to_us = mulhwu_scale_factor(tb_ticks_per_second, 1000000);
> + cpu_khz = tb_ticks_per_second / 1000;
etc
While I really like the idea of adding a cpu_khz platform variable
to ppc32 (my ppc32 perfctr driver has to do horrible things trying
to retrieve the TB and core frequencies), it looks to me as if your
cpu_khz really is the TB frequency not the core frequency. If so,
then please rename it to tb_khz to avoid confusion.
/Mikael
prev parent reply other threads:[~2005-03-08 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 21:48 Frank Rowand
2005-03-08 9:56 ` Mikael Pettersson [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=16941.30406.381804.166260@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=frowand@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®