From: "Remy Bohmer" <linux@bohmer.net>
To: "Haavard Skinnemoen" <hskinnemoen@atmel.com>
Cc: "Andrew Victor" <linux@maxim.org.za>,
linux-arm-kernel@lists.arm.linux.org.uk,
"Russell King" <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, kernel@avr32linux.org
Subject: Re: [PATCH v2 0/6] atmel_serial: Cleanups, irq handler splitup & DMA
Date: Wed, 19 Dec 2007 17:59:09 +0100 [thread overview]
Message-ID: <3efb10970712190859j125eb027y89a967280c2c829@mail.gmail.com> (raw)
In-Reply-To: <20071219174742.68e70c6c@dhcp-252-066.norway.atmel.com>
> > but I noticed that I sometimes get an input overrun (ttyS0: 1
> > input overrun(s) ) during stress conditions.
> > This is something I did not notice before, maybe it was already there,
> > or has something changed in this area that it is now more sensitive
> > for this?
> Hmm...is this with or without DMA?
DBGU is without DMA.
> If it's without DMA, something very strange is going on -- the non-DMA
> RX code is almost the only thing left in the hardirq handler, so I
> would really expect overruns to be much less likely to occur now than
> before...
As mentioned, maybe it was already there, but I did not run into it
earlier. I have to figure that out. But, at 115200 and a 1 byte
receive-'fifo' on DBGU, and still interrupt locks somewhere in the
tree up to 300us, it is a simple calculation that we can run into
overrun conditions...
Notice that without these interrupt handler splitup, it was much, much
much worse...
So, for me it is not a big deal, because it is just a terminal, and
with my shaky fingers I usually do not type that fast ;-))
Remy
Kind Regards,
Remy
next prev parent reply other threads:[~2007-12-19 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 15:12 Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 1/6] atmel_serial: Clean up the code Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 2/6] atmel_serial: Use cpu_relax() when busy-waiting Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 3/6] atmel_serial: Use existing console options only if BRG is running Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 4/6] atmel_serial: Fix bugs in probe() error path and remove() Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 5/6] atmel_serial: Split the interrupt handler Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 6/6] atmel_serial: Add DMA support Haavard Skinnemoen
2007-12-19 15:57 ` [PATCH v2 0/6] atmel_serial: Cleanups, irq handler splitup & DMA Remy Bohmer
2007-12-19 16:09 ` Haavard Skinnemoen
2007-12-19 16:40 ` Remy Bohmer
2007-12-19 16:47 ` Haavard Skinnemoen
2007-12-19 16:59 ` Remy Bohmer [this message]
2007-12-19 17:19 ` Haavard Skinnemoen
2007-12-19 20:32 ` Remy Bohmer
2007-12-22 15:56 ` Haavard Skinnemoen
2007-12-19 22:13 ` Ulf Samuelsson
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=3efb10970712190859j125eb027y89a967280c2c829@mail.gmail.com \
--to=linux@bohmer.net \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
/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
all inboxes | Powered by JetHome®