From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Smolorz Subject: Re: [Xenomai-core] [PATCH] Don't call __ipipe_mach_set_dec in rthal_timer_release directly Date: Wed, 15 Nov 2006 11:25:31 +0100 References: <455AE6D8.8020008@domain.hid> In-Reply-To: <455AE6D8.8020008@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org Gilles Chanteperdrix wrote: > Sebastian Smolorz wrote: > > Gilles Chanteperdrix wrote: > >>You can avoid this problem by adding LATCH or > >>__ipipe_mach_ticks_per_jiffy to the current value of the match register > >>in the timer interrupt, as it is done for the SA and PXA architectures. > > > > Unfortunately, this solution is not applicable. The timers of PXA and SA > > are counting up whereas the S3C24xx timers are counting down to zero. > > There is no match register for the next interrupt. In contrast, the timer > > must be programmed with the new dec value directly, thus stopping it for > > the time of re-programming. > > Right, you are in the same case as the integrator platform. Yes. But I cannot adopt the integrator's re-programming of the timer in the Linux timer interrupt handler because this would lead to lost ticks or rather to longer periods. Therefore I proposed the patch. -- Sebastian