From: Michael Trimarchi <michael@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Adeos <adeos-main@gna.org>, b.morelli@domain.hid
Subject: Re: [Adeos-main] [PATCH 3/3] Fix imx time reprogramming issue
Date: Tue, 24 Apr 2012 10:32:45 +0200 [thread overview]
Message-ID: <4F96652D.1080401@domain.hid> (raw)
In-Reply-To: <4F966094.9070709@domain.hid>
On 04/24/2012 10:13 AM, Gilles Chanteperdrix wrote:
> On 04/24/2012 10:09 AM, Michael Trimarchi wrote:
>> This patch includes:
>>
>> * Fix invalid virtual address base of MX1_2_TCM
>> * Fix the minimum delay below which the hardware timer can not be reprogrammed.
>> The value is the same of that one that is used to calculate the min_delta_ns
>>
>> arch/arm/plat-mxc/time.c
>> 414: clockevent_mxc.min_delta_ns = clockevent_delta2ns(0xff, &clockevent_mxc);
>
> I do not think we can use this value, it is way to high for xenomai
> needs. In latest releases we use 2us instead of 1us, and according to
> what a user posted recently, this should be enough, could you test with
> 2us? And 2us is already what we have in the 3.2 repository.
>
As I understood the min delays is in tick and not depend on the clock rate.
This is from atmel at91_ipipe_time
min_delta_ticks = ((unsigned long long) clkevt.min_delta_ns
* clkevt.mult) >> clkevt.shift;
this is exaclty the reverse calculation of clockevent_mxc.min_delta_ns
I have already the result in the previous calculation: 0xff is the minimun in ticks
Michael
next prev parent reply other threads:[~2012-04-24 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 8:09 [Adeos-main] [PATCH 3/3] Fix imx time reprogramming issue Michael Trimarchi
2012-04-24 8:13 ` Gilles Chanteperdrix
2012-04-24 8:32 ` Michael Trimarchi [this message]
2012-04-24 8:53 ` Gilles Chanteperdrix
2012-04-24 9:31 ` Michael Trimarchi
2012-04-24 9:41 ` Gilles Chanteperdrix
2012-04-24 20:34 ` Gilles Chanteperdrix
2012-04-25 8:12 ` Michael Trimarchi
2012-04-25 8:18 ` 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=4F96652D.1080401@domain.hid \
--to=michael@domain.hid \
--cc=adeos-main@gna.org \
--cc=b.morelli@domain.hid \
--cc=gilles.chanteperdrix@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.