From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Beisert Subject: Re: Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17) Date: Sat, 8 Oct 2011 20:15:16 +0200 Message-ID: <201110082015.17128.jbe@pengutronix.de> References: <201110081326.58731.jbe@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Thomas Gleixner , LKML , "linux-rt-users" , linux-arm-kernel@lists.infradead.org To: Thomas Abraham Return-path: Received: from metis.ext.pengutronix.de ([92.198.50.35]:60610 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753386Ab1JHSPV convert rfc822-to-8bit (ORCPT ); Sat, 8 Oct 2011 14:15:21 -0400 In-Reply-To: Content-Disposition: inline Sender: linux-rt-users-owner@vger.kernel.org List-ID: Hi Thomas, Thomas Abraham wrote: > On 8 October 2011 16:56, Juergen Beisert wrote: > > Thomas Gleixner wrote: > >> I'm pleased to announce the 3.0.6-rt17 release. > > > > I have no idea where to search, but when I'm using the 3.0.6-rt17 o= n my > > Samsung S3C6410 ARM based system, the UART (serial console) does no= t work > > as expected. Typing only one char at a time is okay. Typing two cha= rs > > immediately makes the system using 100 % CPU load and takes about 2 > > seconds to respond. It seems the interrupt handling is broken in th= e UART > > driver, but I don't know how to fix it. > > > > This with a simple cursor up (one char to get the last command) and= a > > small pause to the next "ENTER" char: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > > =A018: =A0 =A05739107 =A0s3c-uart =A0s3c6400-uart > > > > Same again: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > > =A018: =A0 =A05739113 =A0s3c-uart =A0s3c6400-uart > > > > 6 interrupts seems reasonable. > > > > Now with cursor up and SPACE immediately, then a pause for ENTER: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > > =A018: =A0 =A05923815 =A0s3c-uart =A0s3c6400-uart > > > > 184702 interrupts looks strange. > > Just curious, do you have the following two commits? > > serial: samsung: Add unified interrupt handler for s3c64xx and later = SoC's > ARM: SAMSUNG: Remove uart irq handling from platform code Are they part of the current 3.0.6 vanilla kernel? I'm only using the v= anilla=20 3.0.6 with rt17 on my target. jbe --=20 Pengutronix e.K. | Juergen Beisert = | Linux Solutions for Science and Industry | http://www.pengutronix.= de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-rt-user= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: jbe@pengutronix.de (Juergen Beisert) Date: Sat, 8 Oct 2011 20:15:16 +0200 Subject: Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17) In-Reply-To: References: <201110081326.58731.jbe@pengutronix.de> Message-ID: <201110082015.17128.jbe@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Thomas, Thomas Abraham wrote: > On 8 October 2011 16:56, Juergen Beisert wrote: > > Thomas Gleixner wrote: > >> I'm pleased to announce the 3.0.6-rt17 release. > > > > I have no idea where to search, but when I'm using the 3.0.6-rt17 on my > > Samsung S3C6410 ARM based system, the UART (serial console) does not work > > as expected. Typing only one char at a time is okay. Typing two chars > > immediately makes the system using 100 % CPU load and takes about 2 > > seconds to respond. It seems the interrupt handling is broken in the UART > > driver, but I don't know how to fix it. > > > > This with a simple cursor up (one char to get the last command) and a > > small pause to the next "ENTER" char: > > > > root at mini6410:~ cat /proc/interrupts | grep 18: > > ?18: ? ?5739107 ?s3c-uart ?s3c6400-uart > > > > Same again: > > > > root at mini6410:~ cat /proc/interrupts | grep 18: > > ?18: ? ?5739113 ?s3c-uart ?s3c6400-uart > > > > 6 interrupts seems reasonable. > > > > Now with cursor up and SPACE immediately, then a pause for ENTER: > > > > root at mini6410:~ cat /proc/interrupts | grep 18: > > ?18: ? ?5923815 ?s3c-uart ?s3c6400-uart > > > > 184702 interrupts looks strange. > > Just curious, do you have the following two commits? > > serial: samsung: Add unified interrupt handler for s3c64xx and later SoC's > ARM: SAMSUNG: Remove uart irq handling from platform code Are they part of the current 3.0.6 vanilla kernel? I'm only using the vanilla 3.0.6 with rt17 on my target. jbe -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | http://www.pengutronix.de/ | From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753484Ab1JHSPW (ORCPT ); Sat, 8 Oct 2011 14:15:22 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:60609 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753264Ab1JHSPV convert rfc822-to-8bit (ORCPT ); Sat, 8 Oct 2011 14:15:21 -0400 From: Juergen Beisert Organization: Pengutronix - Linux Solutions for Science and Industry To: Thomas Abraham Subject: Re: Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17) Date: Sat, 8 Oct 2011 20:15:16 +0200 User-Agent: KMail/1.9.10 Cc: Thomas Gleixner , LKML , "linux-rt-users" , linux-arm-kernel@lists.infradead.org References: <201110081326.58731.jbe@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <201110082015.17128.jbe@pengutronix.de> X-SA-Exim-Connect-IP: 2001:6f8:1178:4:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: jbe@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, Thomas Abraham wrote: > On 8 October 2011 16:56, Juergen Beisert wrote: > > Thomas Gleixner wrote: > >> I'm pleased to announce the 3.0.6-rt17 release. > > > > I have no idea where to search, but when I'm using the 3.0.6-rt17 on my > > Samsung S3C6410 ARM based system, the UART (serial console) does not work > > as expected. Typing only one char at a time is okay. Typing two chars > > immediately makes the system using 100 % CPU load and takes about 2 > > seconds to respond. It seems the interrupt handling is broken in the UART > > driver, but I don't know how to fix it. > > > > This with a simple cursor up (one char to get the last command) and a > > small pause to the next "ENTER" char: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > >  18:    5739107  s3c-uart  s3c6400-uart > > > > Same again: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > >  18:    5739113  s3c-uart  s3c6400-uart > > > > 6 interrupts seems reasonable. > > > > Now with cursor up and SPACE immediately, then a pause for ENTER: > > > > root@mini6410:~ cat /proc/interrupts | grep 18: > >  18:    5923815  s3c-uart  s3c6400-uart > > > > 184702 interrupts looks strange. > > Just curious, do you have the following two commits? > > serial: samsung: Add unified interrupt handler for s3c64xx and later SoC's > ARM: SAMSUNG: Remove uart irq handling from platform code Are they part of the current 3.0.6 vanilla kernel? I'm only using the vanilla 3.0.6 with rt17 on my target. jbe -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | http://www.pengutronix.de/ |