linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] imx-serial-excessive-status-clearing-on-break.patch
@ 2010-02-01 12:28 Andy Green
  2010-02-15 10:58 ` Andy Green
  0 siblings, 1 reply; 3+ messages in thread
From: Andy Green @ 2010-02-01 12:28 UTC (permalink / raw)
  To: linux-arm-kernel

From: Andy Green <andy.green@txtr.com>

cc: Sasha Hauer <kernel@pengutronix.de>

We noticed that we were only able to communicate once with a GSM module
per session, if we powered down the module then the serial driver was
broken until reset, no traffic or /proc/interrupts activity could be
seen any more.

Volker noticed it was provoked by a long "break" seen on the wire when
the RX was not driven during powerdown, we discovered we could kill the
serial driver just by forcing RX low extenally for a little while.

I saw that the processing for BREAK in the driver gets too excited and
clears down all set bits in USR2, including that a character is pending.
This stops all further characters getting processed.

The attached one-liner makes the serial driver immortal against BREAK.

Signed-off-by: Andy Green <andy.green@txtr.com>
Signed-off-by: Volker Ernst <volker.ernst@txtr.com>
---

 drivers/serial/imx.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/serial/imx.c b/drivers/serial/imx.c
index 18130f1..c5b546a 100644
--- a/drivers/serial/imx.c
+++ b/drivers/serial/imx.c
@@ -440,7 +440,7 @@ static irqreturn_t imx_rxint(int irq, void *dev_id)
 
 		temp = readl(sport->port.membase + USR2);
 		if (temp & USR2_BRCD) {
-			writel(temp | USR2_BRCD, sport->port.membase + USR2);
+			writel(USR2_BRCD, sport->port.membase + USR2);
 			if (uart_handle_break(&sport->port))
 				continue;
 		}

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH] imx-serial-excessive-status-clearing-on-break.patch
  2010-02-01 12:28 [PATCH] imx-serial-excessive-status-clearing-on-break.patch Andy Green
@ 2010-02-15 10:58 ` Andy Green
  2010-02-16 16:19   ` Sascha Hauer
  0 siblings, 1 reply; 3+ messages in thread
From: Andy Green @ 2010-02-15 10:58 UTC (permalink / raw)
  To: linux-arm-kernel

On 02/01/10 13:28, Somebody in the thread at some point said:

> -			writel(temp | USR2_BRCD, sport->port.membase + USR2);
> +			writel(USR2_BRCD, sport->port.membase + USR2);

Hi Sascha -

What is the disposition of this patch?  It solves a real problem in the 
imx serial but it is just sitting there for two weeks.

-Andy

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH] imx-serial-excessive-status-clearing-on-break.patch
  2010-02-15 10:58 ` Andy Green
@ 2010-02-16 16:19   ` Sascha Hauer
  0 siblings, 0 replies; 3+ messages in thread
From: Sascha Hauer @ 2010-02-16 16:19 UTC (permalink / raw)
  To: linux-arm-kernel

Hi Andy,

On Mon, Feb 15, 2010 at 11:58:18AM +0100, Andy Green wrote:
> On 02/01/10 13:28, Somebody in the thread at some point said:
>
>> -			writel(temp | USR2_BRCD, sport->port.membase + USR2);
>> +			writel(USR2_BRCD, sport->port.membase + USR2);
>
> Hi Sascha -
>
> What is the disposition of this patch?  It solves a real problem in the  
> imx serial but it is just sitting there for two weeks.

Sorry, I missed it. Applied now.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-02-16 16:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-01 12:28 [PATCH] imx-serial-excessive-status-clearing-on-break.patch Andy Green
2010-02-15 10:58 ` Andy Green
2010-02-16 16:19   ` Sascha Hauer

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).