Re: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

2009-11-17 Thread Tony Lindgren
* Vikram Pandita vikram.pand...@ti.com [091116 15:00]: OMAP3630 and OMAP4430 UART IP blocks have a restriction wrt RX FIFO. Empty RX fifo read causes an abort. OMAP1/2/3 do not have this restriction. So interoduce a flag in 8250 driver: UPF_NO_EMPTY_FIFO_READ If this flag is specified for

RE: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

2009-11-17 Thread Pandita, Vikram
Tony From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony Lindgren Sent: Tuesday, November 17, 2009 11:06 AM To: Pandita, Vikram Cc: linux-omap@vger.kernel.org; Shilimkar, Santosh Subject: Re: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

Re: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

2009-11-17 Thread Tony Lindgren
Subject: Re: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag * Vikram Pandita vikram.pand...@ti.com [091116 15:00]: OMAP3630 and OMAP4430 UART IP blocks have a restriction wrt RX FIFO. Empty RX fifo read causes an abort. OMAP1/2/3 do not have this restriction. So interoduce a flag

Re: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

2009-11-17 Thread Alan Cox
On Tue, 17 Nov 2009 15:16:55 -0600 Vikram Pandita vikram.pand...@ti.com wrote: OMAP3630 and OMAP4430 UART IP blocks have a restriction wrt RX FIFO. Empty RX fifo read causes an abort. OMAP1/2/3 do not have this restriction. Nothing wrong with the requirement but I think it would keep 8250.c a

RE: [PATCH 1/2] serial: 8250: add UPF_NO_EMPTY_FIFO_READ flag

2009-11-17 Thread Pandita, Vikram
-Original Message- From: Alan Cox [mailto:a...@lxorguk.ukuu.org.uk] Sent: Tuesday, November 17, 2009 3:26 PM To: Pandita, Vikram Cc: linux-ser...@vger.kernel.org; a...@linux-foundation.org; linux-omap@vger.kernel.org; Pandita, Vikram; Shilimkar, Santosh Subject: Re: [PATCH 1/2] serial