linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: schen@mvista.com (Steve Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: atmel_serial losing characters under libmodbus
Date: Wed, 11 Nov 2009 09:09:05 -0600	[thread overview]
Message-ID: <1257952145.3153.705.camel@linux-1lbu> (raw)
In-Reply-To: <4AFAC33B.2090406@gmail.com>

On Wed, 2009-11-11 at 14:59 +0100, Josef Holzmayr wrote:
> christian pellegrin wrote:
> > On Wed, Nov 11, 2009 at 1:44 PM, Josef Holzmayr
> > <zentrale.at.work@gmail.com> wrote:
> >> When using libmodbus on an atmel_serial line, it seems to lose about 1 char
> >> in 50 that it's supposed to receive. This is independet of the baud rate, it
> >> happens everywhere from 2400 to 19200. Full code excerpt from the lib is
> >> below, but basically reading is just an select/read pair. Are there some
> >> known issues with that particular tty device?
> >>
> > 
> > Hi, the only serial port on AT91 that gives me troubles is the DBGU
> > port which shares the interrupt with the timer tick. You see a lot of
> > serial overruns there if you have the kernel compiled with HZ=1000 on
> > that port (usually ttyS0).
> > 
> 
> Thanks for the hint, but iv'e got this problem reproducable on ttyS2 and 
> ttyS4. CONFIG_HZ is 128, and whats really interesting: if you use an 
> usb-to-serial converter instead, everything works like a charm.
> 
I experienced serial port dropping characters at random some time back.
The problem turned out to be FIFO size in software was set larger than
FIFO size in actual hardware...  Just a thought...

Steve

      reply	other threads:[~2009-11-11 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 12:44 atmel_serial losing characters under libmodbus Josef Holzmayr
2009-11-11 13:39 ` christian pellegrin
2009-11-11 13:59   ` Josef Holzmayr
2009-11-11 15:09     ` Steve Chen [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=1257952145.3153.705.camel@linux-1lbu \
    --to=schen@mvista.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).