linux-mips
[Top] [All Lists]

Re: [PATCH 3/5] Deforest the function pointer jungle in the time code.

To: vagabon.xyz@gmail.com
Subject: Re: [PATCH 3/5] Deforest the function pointer jungle in the time code.
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 20 Jun 2007 01:08:05 +0900 (JST)
Cc: ralf@linux-mips.org, macro@linux-mips.org, sshtylyov@ru.mvista.com, linux-mips@linux-mips.org
In-reply-to: <cda58cb80706190033y47ccec58u8fc8254ced24f96f@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <cda58cb80706180238r17da4434jcdee307b0385729b@mail.gmail.com> <20070619.005121.118948229.anemo@mba.ocn.ne.jp> <cda58cb80706190033y47ccec58u8fc8254ced24f96f@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On Tue, 19 Jun 2007 09:33:33 +0200, "Franck Bui-Huu" <vagabon.xyz@gmail.com> 
wrote:
> What do you mean by "pnx8550 can have customized copy of cp0_hpt
> routines" ? Do you mean that it should copy the whole clock event
> driver ?
>
> It seems to me that using cp0 hpt as a clock event only is a valid usage...

Well, I thought the customized cp0 clockevent codes (custom
.set_next_event routine is needed anyway, isn't it?) would be small
enough.  But I did not investigate deeply.  If generic cp0 hpt can
handle this beast without much bloating, it would be great.

---
Atsushi Nemoto

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