From: Tony Lindgren <tony@atomide.com>
To: Vikram Pandita <vikram.pandita@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/2] omap: serial: fix non-empty rx uart fifo abort
Date: Tue, 17 Nov 2009 09:06:46 -0800 [thread overview]
Message-ID: <20091117170646.GD29266@atomide.com> (raw)
In-Reply-To: <1258412036-31986-1-git-send-email-vikram.pandita@ti.com>
* Vikram Pandita <vikram.pandita@ti.com> [091116 15:00]:
> Empty uart rx fifo read can cause omap to abort
> OMAP silicon affected: OMAP3630, OMAP4430
> OMAP silicon not-affected: omap1/2/3
>
> So pass flag UPF_NO_EMPTY_FIFO_READ in plat_serial8250_port, so that 8250
> driver does not abort on empty rx fifo read
>
> Tested on zoom3(3630) board
This too as it depends on the 1/2 patch.
Tony
> Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>
> ---
> arch/arm/mach-omap2/serial.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index 2e17b57..669652b 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -624,8 +624,15 @@ void __init omap_serial_early_init(void)
> uart->p = p;
> list_add_tail(&uart->node, &uart_list);
>
> - if (cpu_is_omap44xx())
> + if (cpu_is_omap44xx()) {
> p->irq += 32;
> + /* Do not read empty UART fifo on omap4 */
> + p->flags |= UPF_NO_EMPTY_FIFO_READ;
> + }
> +
> + /* Do not read empty UART fifo on omap3630 */
> + if (cpu_is_omap3630())
> + p->flags |= UPF_NO_EMPTY_FIFO_READ;
>
> omap_uart_enable_clocks(uart);
> }
> --
> 1.6.5.1.69.g36942
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-17 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 22:53 [PATCH 2/2] omap: serial: fix non-empty rx uart fifo abort Vikram Pandita
2009-11-17 17:06 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 21:17 Vikram Pandita
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=20091117170646.GD29266@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.com \
/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