All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: GUGLIELMO NAVARRA <guglielmo.navarra@studenti.uniparthenope.it>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [Xenomai-help] Latency calculation on da850 (Omap L138)
Date: Sat, 15 Dec 2012 16:59:32 +0100	[thread overview]
Message-ID: <50CC9E64.4030901@xenomai.org> (raw)
In-Reply-To: <7385E066AECB78449EEDFA7EE2A2B2B60A052E0D@DB3PRD0410MB355.eurprd04.prod.outlook.com>

On 12/15/2012 04:45 PM, GUGLIELMO NAVARRA wrote:

> Da: Gilles Chanteperdrix [gilles.chanteperdrix@xenomai.org]
> Inviato: sabato 15 dicembre 2012 15.54
>> Anyway, I also asked you to run the "tsc" test, what does this test tell
>> you?


You are quoting the part about the tsc test, did you try and run it?

> 
> In the structure tsc_info must assign addresses (phy and virt) of timer assigned to clocksource or clockevent?



The tsc is a clocksource. If the tsc is based on a free running counter,
what should be accessed in user-space is the free running counter.
The counter which value changes at 27MHz.
The aim is to have an idea of the current time by reading this register.
I do not know how to explain this in any other way.

> I have assigned the offset of timer assigned to clockevent

> (base address is the same because the timer is 64-bit)

The tsc emulation code does not give a damn about any base address. It
simply needs the address of the counter. Nothing else, nothing more.

> 
> 
> static void l138_xenomai_tsc_init(void)
> {
>    struct davinci_soc_info *soc_info = &davinci_soc_info;
>    struct davinci_timer_instance *dtip = soc_info->timer_info->timers;
>    void __iomem *base;
>    base = ioremap(dtip[0].base, SZ_4K);
>    tsc_info.type = IPIPE_TSC_TYPE_FREERUNNING;
>    tsc_info.freq = l138_clock_tick_rate;
>    tsc_info.counter_vaddr = (unsigned long)(base + TIM12);
>    tsc_info.u.counter_paddr = dtip[0].base + TIM12;
>    tsc_info.u.fr.mask = 0xffffffff;
>    __ipipe_tsc_register(&tsc_info);
> }


If the registers are already ioremapped, please do not remap them a
second time. Also, if the tsc emulation was running correctly in
kernel-space, chances are the kernel-space virtual address was already
correct.

And please keep the mailing list in copy.

-- 
                                                                Gilles.


  parent reply	other threads:[~2012-12-15 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15 12:07 [Xenomai] [Xenomai-help] Latency calculation on da850 (Omap L138) GUGLIELMO NAVARRA
2012-12-15 12:20 ` Gilles Chanteperdrix
     [not found]   ` <7385E066AECB78449EEDFA7EE2A2B2B60A052DA8@DB3PRD0410MB355.eurprd04.prod.outlook.com>
2012-12-15 13:56     ` Gilles Chanteperdrix
2012-12-15 14:06       ` Gilles Chanteperdrix
2012-12-15 14:42         ` GUGLIELMO NAVARRA
2012-12-15 14:50           ` Gilles Chanteperdrix
2012-12-15 14:54           ` Gilles Chanteperdrix
     [not found]             ` <7385E066AECB78449EEDFA7EE2A2B2B60A052E0D@DB3PRD0410MB355.eurprd04.prod.outlook.com>
2012-12-15 15:59               ` Gilles Chanteperdrix [this message]
2012-12-15 12:35 ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2012-12-15 15:47 GUGLIELMO NAVARRA
2012-12-15 15:56 ` GUGLIELMO NAVARRA

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=50CC9E64.4030901@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=guglielmo.navarra@studenti.uniparthenope.it \
    --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.