All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <trimarchimichael@domain.hid>
To: Bosko Radivojevic <bosko.radivojevic@domain.hid>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: david-b@domain.hid, adeos-main@gna.org
Subject: Re: [Adeos-main] at91sam9260
Date: Sat, 9 Feb 2008 12:13:37 +0100 (CET)	[thread overview]
Message-ID: <246938.91746.qm@domain.hid> (raw)
In-Reply-To: <d6c8ef150802081142y54648ecex5b307eb3c25e5086@domain.hid>

Hi,
> Thanks. Actually, I have simillar problems (buffer
> overrun) when working
> with serial port (at91sam9260-ek based board). But,
> I haven't inspected the
> problem more than that. I'll do that next week.
> 
> On Feb 8, 2008 8:36 PM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org>
> wrote:
> 
> >
> > I received a mail from Michael recently telling me
> that he observes the
> > same behaviour with the PREEMPT_RT patch, so the
> I-pipe patch is
> > probably out of cause. He now suspects a hardware
> issue (one serial port
> > pin seems to be shared with another peripheral, as
> I think I understood).
> >
> >
>
I finish my investigation, and I think that depens
only 
in some overhead. In linux is present using hrtimer
and doesn't depends on NO_HZ options. If some hrtimer
is executed with the interrupts disabled and the
serial
must receive a single char, you receive and overrun.
I suppose that the NO_HZ option can be a solution
(less interrupt) but an the end, doesn't change. The
dma
patch on serial device resolve the problem. I think
that for adeos is the same. I try to investigate, how
long is the max blocking time in hrtimer interrupt.

Using TC timer is ok. David and Gilles, you are right
but I want to know how in linux-rt and adeos, I can
reduce the latency to support this interrupts
frquency.

Regards Michael



      ___________________________________ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html


  reply	other threads:[~2008-02-09 11:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 11:10 [Adeos-main] at91sam9260 Michael Trimarchi
2008-02-08 19:21 ` Bosko Radivojevic
2008-02-08 19:36   ` Gilles Chanteperdrix
2008-02-08 19:42     ` Bosko Radivojevic
2008-02-09 11:13       ` Michael Trimarchi [this message]
2008-02-09 13:39         ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2007-12-20 18:44 Michael Trimarchi
2007-12-20 18:54 ` Gilles Chanteperdrix
2007-12-20 19:26 ` Gilles Chanteperdrix
2007-12-26 10:59 ` Gilles Chanteperdrix
2007-12-17 14:51 Michael Trimarchi
2007-12-17 14:20 Michael Trimarchi
2007-12-17 14:42 ` Gilles Chanteperdrix
2007-12-17 21:47 ` Gilles Chanteperdrix
2007-12-17 23:38   ` Gilles Chanteperdrix
2007-12-17 10:23 Michael Trimarchi
2007-12-17 10:26 ` Gilles Chanteperdrix
2007-12-17 14:11 ` Gilles Chanteperdrix
2007-12-15 13:06 Michael Trimarchi
2007-12-15 12:35 Michael Trimarchi
2007-12-14 19:44 Michael Trimarchi
2007-12-14 20:15 ` Gilles Chanteperdrix
2007-12-13 15:41 Michael Trimarchi
2007-12-13 15:27 Michael Trimarchi
2007-12-13 15:32 ` Gilles Chanteperdrix
2007-12-15 11:59 ` Gilles Chanteperdrix
2007-12-11 18:33 Michael Trimarchi
2007-12-11 18:23 Michael Trimarchi
2007-12-11 18:24 ` Gilles Chanteperdrix
2007-12-11 17:19 Michael Trimarchi
2007-12-11 18:14 ` 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=246938.91746.qm@domain.hid \
    --to=trimarchimichael@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=bosko.radivojevic@domain.hid \
    --cc=david-b@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.