From: Nishanth Menon <nm@ti.com>
To: Vikram Pandita <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature
Date: Fri, 20 Nov 2009 10:09:49 -0600 [thread overview]
Message-ID: <4B06BF4D.2090201@ti.com> (raw)
In-Reply-To: <1258732956-18799-2-git-send-email-vikram.pandita@ti.com>
Vikram Pandita had written, on 11/20/2009 10:02 AM, the following:
> Interoduce omap feature OMAP3_HAS_UART_NO_EMPTY_FIFO_READ
^^^^^^^^^ <- you meant introduce
>
> On omap3630/omap4 an empty fifo read causes a crash
>
> Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>
> Ack-by: Menon, Nishanth <nm@ti.com>
^^^^^ <- :P nope you dont have my Acked-by until you change this to
Acked from Ack ;)..
Thanks for the simpler patch.
> ---
> arch/arm/mach-omap2/id.c | 7 +++++++
> arch/arm/plat-omap/include/plat/cpu.h | 2 ++
> 2 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
> index f48a4b2..3e266cd 100644
> --- a/arch/arm/mach-omap2/id.c
> +++ b/arch/arm/mach-omap2/id.c
> @@ -176,6 +176,12 @@ void __init omap3_check_features(void)
> OMAP3_CHECK_FEATURE(status, NEON);
> OMAP3_CHECK_FEATURE(status, ISP);
>
> + /* On omap3630 and omap4: UART empty rx fifo read aborts */
> + if (cpu_is_omap3630())
> + omap3_features |= OMAP3_HAS_UART_NO_EMPTY_FIFO_READ;
> + if (cpu_is_omap44xx())
> + omap3_features |= OMAP3_HAS_UART_NO_EMPTY_FIFO_READ;
> +
> /*
> * TODO: Get additional info (where applicable)
> * e.g. Size of L2 cache.
> @@ -316,6 +322,7 @@ void __init omap3_cpuinfo(void)
> OMAP3_SHOW_FEATURE(sgx);
> OMAP3_SHOW_FEATURE(neon);
> OMAP3_SHOW_FEATURE(isp);
> + OMAP3_SHOW_FEATURE(uart_no_empty_fifo_read);
>
> printk(")\n");
> }
> diff --git a/arch/arm/plat-omap/include/plat/cpu.h b/arch/arm/plat-omap/include/plat/cpu.h
> index 2e17890..c32f015 100644
> --- a/arch/arm/plat-omap/include/plat/cpu.h
> +++ b/arch/arm/plat-omap/include/plat/cpu.h
> @@ -497,6 +497,7 @@ extern u32 omap3_features;
> #define OMAP3_HAS_SGX BIT(2)
> #define OMAP3_HAS_NEON BIT(3)
> #define OMAP3_HAS_ISP BIT(4)
> +#define OMAP3_HAS_UART_NO_EMPTY_FIFO_READ BIT(5)
>
> #define OMAP3_HAS_FEATURE(feat,flag) \
> static inline unsigned int omap3_has_ ##feat(void) \
> @@ -509,5 +510,6 @@ OMAP3_HAS_FEATURE(sgx, SGX)
> OMAP3_HAS_FEATURE(iva, IVA)
> OMAP3_HAS_FEATURE(neon, NEON)
> OMAP3_HAS_FEATURE(isp, ISP)
> +OMAP3_HAS_FEATURE(uart_no_empty_fifo_read, UART_NO_EMPTY_FIFO_READ)
>
> #endif
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-11-20 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 16:02 [PATCH v3 0/2] omap: serial: handle abort on empty rx fifo read Vikram Pandita
2009-11-20 16:02 ` [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature Vikram Pandita
2009-11-20 16:02 ` [PATCH v3 2/2] omap: serial: fix non-empty uart fifo read abort Vikram Pandita
2009-11-20 16:09 ` Nishanth Menon [this message]
2009-11-20 16:14 ` [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature Aguirre, Sergio
2009-11-20 16:16 ` FEATURES - is it good enough (was Re: [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature) Nishanth Menon
2009-11-20 17:06 ` Shilimkar, Santosh
2009-11-20 18:35 ` FEATURES - is it good enough Kevin Hilman
2009-11-20 19:24 ` Nishanth Menon
2009-11-20 19:41 ` Premi, Sanjeev
2009-11-20 19:43 ` Aguirre, Sergio
2009-11-20 20:07 ` Ramirez Luna, Omar
2009-11-20 20:13 ` Aguirre, Sergio
2009-11-20 20:09 ` Nishanth Menon
2009-12-01 15:42 ` Alexander Shishkin
2009-12-02 6:06 ` Menon, Nishanth
2009-12-02 9:05 ` Alexander Shishkin
2009-12-01 13:20 ` [PATCH v3 0/2] omap: serial: handle abort on empty rx fifo read Gadiyar, Anand
2009-12-01 16:05 ` Alexander Shishkin
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=4B06BF4D.2090201@ti.com \
--to=nm@ti.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;
as well as URLs for NNTP newsgroup(s).