From: Sergio Aguirre <saaguirre@ti.com>
To: linux-omap@vger.kernel.org
Cc: Sergio Aguirre <saaguirre@ti.com>
Subject: [RFC part1/2 merge][PATCH 07/10] omap3: zoom2/3 / 3630sdp: Don't init always all uarts
Date: Wed, 3 Mar 2010 08:18:42 -0600 [thread overview]
Message-ID: <1267625925-22616-8-git-send-email-saaguirre@ti.com> (raw)
In-Reply-To: <1267625925-22616-1-git-send-email-saaguirre@ti.com>
This is useless, since in Zoom2/3 boards, the ports aren't even
physically accessible.
They must be explicitly initted in the board-zoom2.c, board-zoom3.c
and board-3630sdp.c files instead.
Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
mode change 100755 => 100644 arch/arm/mach-omap2/board-zoom-peripherals.c
diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c b/arch/arm/mach-omap2/board-zoom-peripherals.c
old mode 100755
new mode 100644
index ca95d8d..6b39849
--- a/arch/arm/mach-omap2/board-zoom-peripherals.c
+++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
@@ -280,7 +280,6 @@ static void enable_board_wakeup_source(void)
void __init zoom_peripherals_init(void)
{
omap_i2c_init();
- omap_serial_init();
usb_musb_init(&musb_board_data);
enable_board_wakeup_source();
}
--
1.6.3.3
next prev parent reply other threads:[~2010-03-03 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 14:18 [RFC part1/2 merge][PATCH 00/10] omap2/3/4: uart4 fixes + zoom2/3 changes Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 01/10] OMAP3: serial: Check for zero-based physical addr Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 02/10] omap2/3/4: serial: Remove condition for getting uart4_phys Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 03/10] ARM: OMAP3630: PRCM: Add UART4 control bits Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 04/10] OMAP clock: Add uart4_ick/fck definitions for 3630 Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 05/10] OMAP3: PRCM: Consider UART4 for 3630 chip in prcm_setup_regs Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 06/10] omap3: serial: Fix uart4 handling for 3630 Sergio Aguirre
2010-03-05 22:37 ` Kevin Hilman
2010-03-05 23:11 ` Aguirre, Sergio
2010-03-08 16:44 ` Aguirre, Sergio
2010-03-08 16:52 ` Kevin Hilman
2010-03-08 16:57 ` Aguirre, Sergio
2010-03-03 14:18 ` Sergio Aguirre [this message]
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 08/10] omap3: 3630sdp: Explicitly enable all UARTs Sergio Aguirre
2010-03-03 14:35 ` Aguirre, Sergio
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 09/10] omap3: zoom 2/3: Change debugboard serial port id Sergio Aguirre
2010-03-03 14:18 ` [RFC part1/2 merge][PATCH 10/10] omap3: zoom2/3: Register only 1 8250 port Sergio Aguirre
2010-03-05 22:40 ` [RFC part1/2 merge][PATCH 00/10] omap2/3/4: uart4 fixes + zoom2/3 changes Kevin Hilman
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=1267625925-22616-8-git-send-email-saaguirre@ti.com \
--to=saaguirre@ti.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.