Re: clockevent questions

2007-05-16 Thread Thomas Gleixner
On Wed, 2007-05-16 at 09:42 +0200, Francis Moreau wrote: > > On Tue, 2007-05-15 at 10:47 +0200, Francis Moreau wrote: > > > My question is about the clock resolution field which is equal to 1ns. > > > How is this possible since my timer's frequency is only 100Mhz ? > > > > you are right. It is a bi

Re: clockevent questions

2007-05-16 Thread Francis Moreau
Hi Thomas, On 5/16/07, Thomas Gleixner <[EMAIL PROTECTED]> wrote: Francis, On Tue, 2007-05-15 at 10:47 +0200, Francis Moreau wrote: > My question is about the clock resolution field which is equal to 1ns. > How is this possible since my timer's frequency is only 100Mhz ? you are right. It is a

Re: clockevent questions

2007-05-15 Thread Thomas Gleixner
Francis, On Tue, 2007-05-15 at 10:47 +0200, Francis Moreau wrote: > My question is about the clock resolution field which is equal to 1ns. > How is this possible since my timer's frequency is only 100Mhz ? you are right. It is a bit strange. The resolution info is not really reflecting the clock

Re: clockevent questions

2007-05-15 Thread Francis Moreau
Thomas, On 5/12/07, Thomas Gleixner <[EMAIL PROTECTED]> wrote: Well, it ends up in hrtimer_interrupt() and the code there finds out, that the next timer is not due right now, so it simply requests the same (absolute) time event again, which is processed by the clock events code and eventually li

Re: clockevent questions

2007-05-12 Thread Francis Moreau
On 5/12/07, Thomas Gleixner <[EMAIL PROTECTED]> wrote: On Sat, 2007-05-12 at 22:13 +0200, Francis Moreau wrote: > > Yes, it is correct. The generic timer code requests an event in the > > future. It does not care, whether the hardware device can handle that or > > not. So the clock event code lim

Re: clockevent questions

2007-05-12 Thread Thomas Gleixner
On Sat, 2007-05-12 at 22:13 +0200, Francis Moreau wrote: > > Yes, it is correct. The generic timer code requests an event in the > > future. It does not care, whether the hardware device can handle that or > > not. So the clock event code limits the delta to the maximum delta the > > device can han

Re: clockevent questions

2007-05-12 Thread Francis Moreau
Hi Thomas, Thanks for answering so quickly ! On 5/12/07, Thomas Gleixner <[EMAIL PROTECTED]> wrote: Francis, On Sat, 2007-05-12 at 16:54 +0200, Francis Moreau wrote: > I'm trying to use clocksource and clockevent new subsystem. My > platform has a timer that I'd like to use both as a clocksour

Re: clockevent questions

2007-05-12 Thread Thomas Gleixner
Francis, On Sat, 2007-05-12 at 16:54 +0200, Francis Moreau wrote: > I'm trying to use clocksource and clockevent new subsystem. My > platform has a timer that I'd like to use both as a clocksource and a > clockevent devices. See arch/i386/kernel/hpet.c > This timer is continueous in sense that i