From: Kevin Hilman <khilman@deeprootsystems.com>
To: Syed Rafiuddin <rafiuddin.syed@ti.com>
Cc: "linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/2][RFC] OMAP4: UART4 Support for OMAP_4430SDP.
Date: Tue, 12 May 2009 07:32:52 -0700 [thread overview]
Message-ID: <877i0mfl2j.fsf@deeprootsystems.com> (raw)
In-Reply-To: <55287.192.168.10.89.1242109234.squirrel@dbdmail.itg.ti.com> (Syed Rafiuddin's message of "Tue\, 12 May 2009 11\:50\:34 +0530 \(IST\)")
"Syed Rafiuddin" <rafiuddin.syed@ti.com> writes:
> This patch enables support for UART4 on OMAP4430 development platform.
>
> Signed-off-by: Syed Rafiuddin <rafiuddin.syed@ti.com>
> ---
> arch/arm/mach-omap2/board-4430sdp.c | 2 +-
> arch/arm/mach-omap2/serial.c | 12 ++++++++++++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> Index: linux-2.6/arch/arm/mach-omap2/board-4430sdp.c
> ===================================================================
> --- linux-2.6.orig/arch/arm/mach-omap2/board-4430sdp.c 2009-05-12
> 10:43:41.000000000 +0530
> +++ linux-2.6/arch/arm/mach-omap2/board-4430sdp.c 2009-05-12 11:40:54.000000000
> +0530
> @@ -38,7 +38,7 @@
> };
>
> static struct omap_uart_config sdp4430_uart_config __initdata = {
> - .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2)),
> + .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2) | (1 << 3)),
> };
>
> static struct omap_lcd_config sdp4430_lcd_config __initdata = {
> Index: linux-2.6/arch/arm/mach-omap2/serial.c
> ===================================================================
> --- linux-2.6.orig/arch/arm/mach-omap2/serial.c 2009-05-12 11:35:55.000000000
> +0530
> +++ linux-2.6/arch/arm/mach-omap2/serial.c 2009-05-12 11:46:13.000000000 +0530
> @@ -53,8 +53,20 @@
> .iotype = UPIO_MEM,
> .regshift = 2,
> .uartclk = OMAP24XX_BASE_BAUD * 16,
> +
> + }, {
> +#ifdef CONFIG_ARCH_OMAP4
> + .membase = IO_ADDRESS(OMAP_UART3_BASE),
> + .mapbase = OMAP_UART4_BASE,
> + .irq = 70,
> + .flags = UPF_BOOT_AUTOCONF,
> + .iotype = UPIO_MEM,
> + .regshift = 2,
> + .uartclk = OMAP24XX_BASE_BAUD * 16,
> }, {
> +#else
> .flags = 0
> +#endif
> }
> };
You dropped the terminator entry (flags == 0) in the OMAP4 case. That
should remain the last entry whether or not OMAP4 support is enabled.
Kevin
next prev parent reply other threads:[~2009-05-12 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51950.192.168.10.89.1241612607.squirrel@dbdmail.itg.ti.com>
2009-05-12 6:20 ` [PATCH 2/2][RFC] OMAP4: UART4 Support for OMAP_4430SDP Syed Rafiuddin
2009-05-12 6:44 ` Shilimkar, Santosh
2009-05-12 14:32 ` Kevin Hilman [this message]
2009-05-12 6:40 vimal singh
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=877i0mfl2j.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=rafiuddin.syed@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