linux-mips
[Top] [All Lists]

Re: 2.6.19 timer API changes

To: sshtylyov@ru.mvista.com
Subject: Re: 2.6.19 timer API changes
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 20 Dec 2006 01:29:16 +0900 (JST)
Cc: danieljlaird@hotmail.com, linux-mips@linux-mips.org, vwool@ru.mvista.com
In-reply-to: <45880AC4.5010403@ru.mvista.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <7943218.post@talk.nabble.com> <20061219.233410.25911550.anemo@mba.ocn.ne.jp> <45880AC4.5010403@ru.mvista.com>
Sender: linux-mips-bounce@linux-mips.org
On Tue, 19 Dec 2006 18:52:36 +0300, Sergei Shtylyov <sshtylyov@ru.mvista.com> 
wrote:
>     I would like to discourage you from repeating those JMR3927
> clocksource "tricks" when you have 3 spare count/compare regs. This
> will warrant troubles when clockevents support gets merged into
> mainline (in fact, it was not necessary even on JMR3927 which has 3
> timers). Although, if the timer isn't auto-reloading (I assume it
> isn't), the trick shouldn't be needed.

Indeed.  JMR3927 is not good for reference on writing new code.

Though I do not know the PNX8550 timer details, if writing to the
COMPARE reset the COUNTER or COUNTER wrapped to zero at a value in
COMPARE, perhaps we can not use c0_hpt_read for clocksource.

---
Atsushi Nemoto

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