2019-05-27 14:55:01 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* Copyright 2001 MontaVista Software Inc.
|
|
|
|
* Author: Jun Sun, jsun@mvista.com or jsun@junsun.net
|
|
|
|
* Copyright (c) 2003, 2004 Maciej W. Rozycki
|
|
|
|
*
|
2007-10-31 00:21:03 +08:00
|
|
|
* Common time service routines for MIPS machines.
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
2007-10-26 20:24:06 +08:00
|
|
|
#include <linux/bug.h>
|
2007-10-12 06:46:09 +08:00
|
|
|
#include <linux/clockchips.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/sched.h>
|
|
|
|
#include <linux/param.h>
|
|
|
|
#include <linux/time.h>
|
|
|
|
#include <linux/timex.h>
|
|
|
|
#include <linux/smp.h>
|
|
|
|
#include <linux/spinlock.h>
|
2011-07-24 04:30:40 +08:00
|
|
|
#include <linux/export.h>
|
2020-05-21 22:07:22 +08:00
|
|
|
#include <linux/cpufreq.h>
|
|
|
|
#include <linux/delay.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
#include <asm/cpu-features.h>
|
2013-09-17 16:25:47 +08:00
|
|
|
#include <asm/cpu-type.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
#include <asm/div64.h>
|
|
|
|
#include <asm/time.h>
|
|
|
|
|
2020-05-21 22:07:22 +08:00
|
|
|
#ifdef CONFIG_CPU_FREQ
|
|
|
|
|
|
|
|
static DEFINE_PER_CPU(unsigned long, pcp_lpj_ref);
|
|
|
|
static DEFINE_PER_CPU(unsigned long, pcp_lpj_ref_freq);
|
|
|
|
static unsigned long glb_lpj_ref;
|
|
|
|
static unsigned long glb_lpj_ref_freq;
|
|
|
|
|
|
|
|
static int cpufreq_callback(struct notifier_block *nb,
|
|
|
|
unsigned long val, void *data)
|
|
|
|
{
|
|
|
|
struct cpufreq_freqs *freq = data;
|
|
|
|
struct cpumask *cpus = freq->policy->cpus;
|
|
|
|
unsigned long lpj;
|
|
|
|
int cpu;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Skip lpj numbers adjustment if the CPU-freq transition is safe for
|
|
|
|
* the loops delay. (Is this possible?)
|
|
|
|
*/
|
|
|
|
if (freq->flags & CPUFREQ_CONST_LOOPS)
|
|
|
|
return NOTIFY_OK;
|
|
|
|
|
|
|
|
/* Save the initial values of the lpjes for future scaling. */
|
|
|
|
if (!glb_lpj_ref) {
|
|
|
|
glb_lpj_ref = boot_cpu_data.udelay_val;
|
|
|
|
glb_lpj_ref_freq = freq->old;
|
|
|
|
|
|
|
|
for_each_online_cpu(cpu) {
|
|
|
|
per_cpu(pcp_lpj_ref, cpu) =
|
|
|
|
cpu_data[cpu].udelay_val;
|
|
|
|
per_cpu(pcp_lpj_ref_freq, cpu) = freq->old;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Adjust global lpj variable and per-CPU udelay_val number in
|
|
|
|
* accordance with the new CPU frequency.
|
|
|
|
*/
|
|
|
|
if ((val == CPUFREQ_PRECHANGE && freq->old < freq->new) ||
|
|
|
|
(val == CPUFREQ_POSTCHANGE && freq->old > freq->new)) {
|
|
|
|
loops_per_jiffy = cpufreq_scale(glb_lpj_ref,
|
|
|
|
glb_lpj_ref_freq,
|
|
|
|
freq->new);
|
|
|
|
|
|
|
|
for_each_cpu(cpu, cpus) {
|
|
|
|
lpj = cpufreq_scale(per_cpu(pcp_lpj_ref, cpu),
|
|
|
|
per_cpu(pcp_lpj_ref_freq, cpu),
|
|
|
|
freq->new);
|
|
|
|
cpu_data[cpu].udelay_val = (unsigned int)lpj;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return NOTIFY_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct notifier_block cpufreq_notifier = {
|
|
|
|
.notifier_call = cpufreq_callback,
|
|
|
|
};
|
|
|
|
|
|
|
|
static int __init register_cpufreq_notifier(void)
|
|
|
|
{
|
|
|
|
return cpufreq_register_notifier(&cpufreq_notifier,
|
|
|
|
CPUFREQ_TRANSITION_NOTIFIER);
|
|
|
|
}
|
|
|
|
core_initcall(register_cpufreq_notifier);
|
|
|
|
|
|
|
|
#endif /* CONFIG_CPU_FREQ */
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* forward reference
|
|
|
|
*/
|
|
|
|
DEFINE_SPINLOCK(rtc_lock);
|
2007-10-12 06:46:08 +08:00
|
|
|
EXPORT_SYMBOL(rtc_lock);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-04-02 07:58:38 +08:00
|
|
|
static int null_perf_irq(void)
|
2005-12-09 20:29:38 +08:00
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 21:55:46 +08:00
|
|
|
int (*perf_irq)(void) = null_perf_irq;
|
2005-12-09 20:29:38 +08:00
|
|
|
|
|
|
|
EXPORT_SYMBOL(perf_irq);
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* time_init() - it does the following things.
|
|
|
|
*
|
2007-10-12 06:46:08 +08:00
|
|
|
* 1) plat_time_init() -
|
2013-01-22 19:59:30 +08:00
|
|
|
* a) (optional) set up RTC routines,
|
|
|
|
* b) (optional) calibrate and set the mips_hpt_frequency
|
2006-10-23 23:21:27 +08:00
|
|
|
* (only needed if you intended to use cpu counter as timer interrupt
|
|
|
|
* source)
|
2007-10-12 06:46:08 +08:00
|
|
|
* 2) calculate a couple of cached variables for later usage
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
unsigned int mips_hpt_frequency;
|
2017-03-14 18:15:31 +08:00
|
|
|
EXPORT_SYMBOL_GPL(mips_hpt_frequency);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-11-22 00:39:44 +08:00
|
|
|
static __init int cpu_has_mfc0_count_bug(void)
|
|
|
|
{
|
|
|
|
switch (current_cpu_type()) {
|
|
|
|
case CPU_R4000PC:
|
|
|
|
case CPU_R4000SC:
|
|
|
|
case CPU_R4000MC:
|
|
|
|
/*
|
|
|
|
* V3.0 is documented as suffering from the mfc0 from count bug.
|
2013-01-22 19:59:30 +08:00
|
|
|
* Afaik this is the last version of the R4000. Later versions
|
2007-11-22 00:39:44 +08:00
|
|
|
* were marketed as R4400.
|
|
|
|
*/
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
case CPU_R4400PC:
|
|
|
|
case CPU_R4400SC:
|
|
|
|
case CPU_R4400MC:
|
|
|
|
/*
|
2011-03-31 09:57:33 +08:00
|
|
|
* The published errata for the R4400 up to 3.0 say the CPU
|
2007-11-22 00:39:44 +08:00
|
|
|
* has the mfc0 from count bug.
|
|
|
|
*/
|
|
|
|
if ((current_cpu_data.processor_id & 0xff) <= 0x30)
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
/*
|
2008-01-05 06:38:31 +08:00
|
|
|
* we assume newer revisions are ok
|
2007-11-22 00:39:44 +08:00
|
|
|
*/
|
2008-01-05 06:38:31 +08:00
|
|
|
return 0;
|
2007-11-22 00:39:44 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2007-10-12 06:46:08 +08:00
|
|
|
void __init time_init(void)
|
|
|
|
{
|
|
|
|
plat_time_init();
|
2005-04-17 06:20:36 +08:00
|
|
|
|
MIPS: R4k clock source initialization bug fix
This is a fix for a bug introduced with commit
447cdf2628b59aa513a42785450b348dced26d8a, submitted as archived here:
http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=20080312235002.c717dde3.yoichi_yuasa%40tripeaks.co.jp
regrettably with no further explanation.
The issue is with the CP0 Count register read erratum present on R4000 and
some R4400 processors. If this erratum is present, then a read from this
register that happens around the time it reaches the value stored in the
CP0 Compare register causes a CP0 timer interrupt that is supposed to
happen when the values in the two registers match to be missed. The
implication for the chips affected is the CP0 timer can be used either as
a source of a timer interrupt (a clock event) or as a source of a
high-resolution counter (a clock source), but not both at a time.
The erratum does not affect timer interrupt operation itself, because in
this case the CP0 Count register is only read while the timer interrupt
has already been raised, while high-resolution counter references happen
at random times.
Additionally some systems apparently have issues with the timer interrupt
line being routed externally and not following the usual CP0 Count/Compare
semantics. In this case we don't want to use the R4k clock event.
We've meant to address the erratum and the timer interrupt routing issue
in time_init, however the commit referred to above broke our solution.
What we currently have is we enable the R4k clock source if the R4k clock
event initialization has succeeded (the timer is present and has no timer
interrupt routing issue) or there is no CP0 Count register read erratum.
Which gives the following boolean matrix:
clock event | count erratum => clock source
------------+---------------+--------------
0 | 0 | 1 (OK)
0 | 1 | 0 (bug!) -> no interference, could use
1 | 0 | 1 (OK)
1 | 1 | 1 (bug!) -> can't use, interference
What we want instead is to enable the R4k clock source if there is no CP0
Count register read erratum (obviously) or the R4k clock event
initialization has *failed* -- because in the latter case we won't be
using the timer interrupt anyway, so we don't care about any interference
CP0 Count reads might cause with the interrupt. This corresponds to the
following boolean matrix:
clock event | count erratum => clock source
------------+---------------+--------------
0 | 0 | 1
0 | 1 | 1
1 | 0 | 1
1 | 1 | 0
This is implemented here, effectively reverting the problematic commit,
and a short explanation is given next to code modified so that the
rationale is known to future readers and confusion is prevented from
happening here again.
It is worth noting that mips_clockevent_init returns 0 upon success while
cpu_has_mfc0_count_bug returns 0 upon failure. This is because the former
function returns an error code while the latter returns a boolean value.
To signify the difference I have therefore chosen to compare the result of
the former call explicitly against 0.
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/5799/
2013-09-03 08:29:58 +08:00
|
|
|
/*
|
|
|
|
* The use of the R4k timer as a clock event takes precedence;
|
|
|
|
* if reading the Count register might interfere with the timer
|
|
|
|
* interrupt, then we don't use the timer as a clock source.
|
|
|
|
* We may still use the timer as a clock source though if the
|
|
|
|
* timer interrupt isn't reliable; the interference doesn't
|
|
|
|
* matter then, because we don't use the interrupt.
|
|
|
|
*/
|
|
|
|
if (mips_clockevent_init() != 0 || !cpu_has_mfc0_count_bug())
|
2007-10-31 00:21:03 +08:00
|
|
|
init_mips_clocksource();
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|