From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Thomas Petazzoni <thomas@free-electrons.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Boris Brezillon <boris@free-electrons.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
xenomai@xenomai.org
Subject: Re: [Xenomai] [PATCH] AT91: SAMA5D3: Adapt Ipipe for AIC5
Date: Fri, 18 Jul 2014 00:21:47 +0200 [thread overview]
Message-ID: <53C84C7B.3060903@xenomai.org> (raw)
In-Reply-To: <20140717115915.GD20328@lukather>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/17/2014 01:59 PM, Maxime Ripard wrote:
> On Thu, Jul 17, 2014 at 12:54:10PM +0200, Gilles Chanteperdrix
> wrote:
>>> Which brings an extra question about this. Is the timer
>>> calibration supposed to get a minimum latency to 0 (meaning
>>> that with a properly calibrated timer, we would only get
>>> positive latencies), or that the average latency should be
>>> around 0 (which would mean that negative latencies would
>>> actually be frequent, but would break the clock_nanosleep
>>> documented behaviour).
>>>
>>> I'm actually seeing the former, but trying the latter only
>>> brings us quite close to having the calibration disabled
>>> entirely.
>>
>> The calibration is left entirely to the user, so, you choose what
>> is best for your application. But indeed, if your application
>> relies on clock_nanosleep documented behaviour (should never
>> wake-up early except in case of signal), you want to set
>> /proc/xenomai/latency value to the minimum value measured by the
>> latency test, minus a safety margin.
>
> Ok, thanks!
>
> I guess you can add my Tested-by tag to your patch, if that makes
> any sense for Xenomai.
We do not consistently use the signed-off mechanism, but I have added
your Tested-by anyway, thanks.
- --
Gilles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iD8DBQFTyEx6GpcgE6m/fboRArMCAJ4396+Bx1OWjJarJtUYFANN2qs7VACfbkNK
0t/vZA4zO0W8kfv6cVGVA48=
=OODg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-07-17 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 10:27 [Xenomai] [PATCH] AT91: SAMA5D3: Adapt Ipipe for AIC5 Maxime Ripard
2014-07-01 10:59 ` Gilles Chanteperdrix
2014-07-01 14:15 ` Maxime Ripard
2014-07-01 19:35 ` Gilles Chanteperdrix
2014-07-04 9:27 ` Maxime Ripard
2014-07-05 8:13 ` Gilles Chanteperdrix
2014-07-07 16:02 ` Maxime Ripard
2014-07-07 16:07 ` Gilles Chanteperdrix
2014-07-08 12:55 ` Maxime Ripard
2014-07-08 14:04 ` Maxime Ripard
2014-07-08 17:30 ` Gilles Chanteperdrix
2014-07-10 15:05 ` Maxime Ripard
2014-07-10 17:04 ` Gilles Chanteperdrix
2014-07-16 16:18 ` Maxime Ripard
2014-07-16 19:47 ` Gilles Chanteperdrix
2014-07-17 10:18 ` Maxime Ripard
2014-07-17 10:54 ` Gilles Chanteperdrix
2014-07-17 11:59 ` Maxime Ripard
2014-07-17 22:21 ` Gilles Chanteperdrix [this message]
2014-07-10 18:27 ` Gilles Chanteperdrix
[not found] ` <20140710172702.5ba6511c@free-electrons.com>
2014-07-10 18:30 ` Gilles Chanteperdrix
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=53C84C7B.3060903@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris@free-electrons.com \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
--cc=thomas@free-electrons.com \
--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.