Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754374AbXLSRUO (ORCPT ); Wed, 19 Dec 2007 12:20:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750920AbXLSRUB (ORCPT ); Wed, 19 Dec 2007 12:20:01 -0500 Received: from nat-132.atmel.no ([80.232.32.132]:63022 "EHLO relay.atmel.no" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750760AbXLSRUA (ORCPT ); Wed, 19 Dec 2007 12:20:00 -0500 Date: Wed, 19 Dec 2007 18:19:15 +0100 From: Haavard Skinnemoen To: "Remy Bohmer" Cc: "Andrew Victor" , linux-arm-kernel@lists.arm.linux.org.uk, "Russell King" , linux-kernel@vger.kernel.org, kernel@avr32linux.org Subject: Re: [PATCH v2 0/6] atmel_serial: Cleanups, irq handler splitup & DMA Message-ID: <20071219181915.71e9daeb@dhcp-252-066.norway.atmel.com> In-Reply-To: <3efb10970712190859j125eb027y89a967280c2c829@mail.gmail.com> References: <1198077130-9021-1-git-send-email-hskinnemoen@atmel.com> <3efb10970712190757m18f8851cq54061ff109790805@mail.gmail.com> <20071219170935.4df62471@dhcp-252-066.norway.atmel.com> <3efb10970712190840m39876762yb4d31c36723c3b8a@mail.gmail.com> <20071219174742.68e70c6c@dhcp-252-066.norway.atmel.com> <3efb10970712190859j125eb027y89a967280c2c829@mail.gmail.com> Organization: Atmel Norway X-Mailer: Claws Mail 3.1.0 (GTK+ 2.12.1; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1834 Lines: 49 On Wed, 19 Dec 2007 17:59:09 +0100 "Remy Bohmer" wrote: > > > 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. Right. > > 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... preempt-rt can disable interrupts for 300 us? If so, then I guess there's really no way to avoid a few overruns. > Notice that without these interrupt handler splitup, it was much, much > much worse... Ok, that's good I guess. > 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 ;-)) If you do, you just need to switch to one of the USARTs instead of the DBGU so that you can use DMA :-) We need to fix the break- and error handling though. But my vacation starts tomorrow, so I probably won't be able to fix it until next year. Haavard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/