All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org, xenomai@xenomai.org
Subject: Re: [Xenomai-core] Clockevent/clocksource.
Date: Mon, 25 Feb 2008 08:35:57 +0100	[thread overview]
Message-ID: <18370.28637.712187.701463@domain.hid> (raw)
In-Reply-To: <18369.59855.128681.821895@domain.hid>

Gilles Chanteperdrix wrote:
 > Philippe Gerum wrote:
 >  > Gilles Chanteperdrix wrote:
 >  > > Hi,
 >  > > 
 >  > > I would like to implement the (I-pipe) AT91 timer management as
 >  > > clocksource/clockevent, however, I have a question, how does one choose
 >  > > the "shift" value in struct clocksource and struct clock_event_device ?
 >  > > 
 >  > 
 >  > http://ixlabs.cs.pub.ro/category/projects/linux-kernel-library/
 > 
 > Looks like the thing is working. A concern though: the hardware timer
 > used on AT91 wraps fast, so if we want the tsc to work correctly, the
 > timer needs to tick every 20ms (which makes using the clock events
 > framework pretty useless, but it is mostly useful for other reasons: it
 > allows me to test Xenomai on ARM in the clock events case). I have set
 > the clock event max_delta_ns member to these 20ms, however when
 > inserting the nucleus module, the max_delta_ns member is set to
 > ULONG_MAX, so my question is: will the nucleus take care of ticking
 > every 20ms ?

Ok. This is now how max_delta_ns is supposed to be used anyway: enabling
NO_HZ breaks the tsc, even if max_delta_ns is not set to ULONG_MAX.

-- 


					    Gilles Chanteperdrix.


      reply	other threads:[~2008-02-25  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 16:46 [Xenomai-core] Clockevent/clocksource Gilles Chanteperdrix
2008-02-24 17:24 ` Philippe Gerum
2008-02-24 22:03   ` Gilles Chanteperdrix
2008-02-25  7:35     ` Gilles Chanteperdrix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18370.28637.712187.701463@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.