[Top] [All Lists]

Re: 2.6.19 timer API changes

Subject: Re: 2.6.19 timer API changes
From: Daniel Laird <>
Date: Wed, 20 Dec 2006 01:37:17 -0800 (PST)
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <>

Atsushi Nemoto wrote:
> <snip>
> Hm, then it seems writing to COMPARE does not clear COUNT.
> How about this?  You should still fix pnx8550_hpt_read() anyway, but I
> suppose gettimeofday() on PNX8550 was broken long time.
> Subject: [MIPS] Use custom timer_ack and for PNX8550

I have not tried the suggested change yet, but I have fiund the mips manual
and here is what it says:

The 32-bit register is both readable and writable through the MTC0 and MFC0
instructions as CP0 register 9. Upon reset, the Count register is set to 0.
Count and Compare together make up Timer_1 in the PR4450 (see Section 3.12).
The timer is active by default. When active, Count register contains a free
counter; on each processor clock-tick, the value in the register increments
by one.
However, when bit ST1 bit[3] in the CP0 Configuration register is enabled,
the timer is
stopped. When the ST1 bit is disabled, the timer returns to its default
Timer_1 is active when the PR4450 is in Sleep mode, but is switched off when
PR4450 is in Coma mode.
When active, the register can be reset with the assertion of the Terminal
(TC_1) signal, which is asserted when the values in the Count and Compare
match. After the Count register is reset, it restarts its count on the next
In the PR4450, the TC_1 signal is fed to the external hardware interrupt
signal to
invoke an interrupt handler e.g., the timer interrupt. The TC_1 signal can
only be
reset to 0 when the interrupt handler performs a write to the Compare
Consecutive writes to Count will result in undefined contents. At least one
must be inserted between consecutive writes to Count.

This seems to suggest that writing to the compare register does in fact
clear count.
If I do the following:
static void __init c0_hpt_timer_init(void)
#ifdef CONFIG_SOC_PNX8550 /* pnx8550 resets to zero */
    expirelo = cycles_per_jiffy;
    expirelo = read_c0_count() + cycles_per_jiffy;
    write_c0_count(cycles_per_jiffy); //Added DJL
Then I get  a normal startup.  i.e it boots fast (no 10second hang).  If I
remove the write_c0_count then I get the 10 second hang.
I have no idea if gettimeofday is broken.  ANy ideas on testing this? Is
there a test package / application that will do this?  Before I write my own

Thanks for the suggestions keep them coming!

View this message in context:
Sent from the linux-mips main mailing list archive at

<Prev in Thread] Current Thread [Next in Thread>