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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello, I wrote:

On Tue, 19 Jun 2007 09:33:33 +0200, "Franck Bui-Huu" <vagabon.xyz@xxxxxxxxx> 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?)

I don't think so.

hpt-cp0.c clock event part doesn't care if the counter is cleared when
an interrupt is triggered.

Well, in the generic case it must read back the Count reg. before writing to the Compare reg. and for PNX8550 this is unnecessary -- but indeed, should not harm...

Well, I was thinking the counter stops at 0 after being clearesd by the match when writing this, which is not the case. So, ignore this sentese.

WBR, Sergei


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux