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

[Sergei Shtylyov <sshtylyov@ru.mvista.com>]

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