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: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Date: Tue, 19 Jun 2007 20:22:59 +0400
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, ralf@linux-mips.org, macro@linux-mips.org, linux-mips@linux-mips.org
In-reply-to: <20070620.010805.23009775.anemo@mba.ocn.ne.jp>
Organization: MontaVista Software Inc.
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> <20070620.010805.23009775.anemo@mba.ocn.ne.jp>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803
Atsushi Nemoto 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.

IMO, the generic code should only have the standard MIPS count/compare support and let the platform code to initialize it if it choses so and also register its own specific clock[source|event] devices if it choses so -- i.e *not* what the current clocksource code does...

---
Atsushi Nemoto

WBR, Sergei

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