From: Tony Lindgren <tony@atomide.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Sonasath, Moiz" <m-sonasath@ti.com>,
"Pandita, Vikram" <vikram.pandita@ti.com>
Subject: Re: [PATCH] omap2/3/4: serial: Half revert multiboot changes
Date: Wed, 24 Feb 2010 08:21:29 -0800 [thread overview]
Message-ID: <20100224162129.GO28173@atomide.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE8944538C6D6A@dlee02.ent.ti.com>
* Aguirre, Sergio <saaguirre@ti.com> [100223 23:37]:
> Hmm..
>
> I think I sent this patch too soon...
>
> Please ignore it, this is not a proper solution I feel..
>
> But what it is true... is that, patch "omap2/3/4: Fix mach-omap2/serial.c for multiboot" is definitely breaking Zoom3 boot, and needs to be fixed.
Yes sounds like only zoom has the external uart, other 3630
boards may be using the internal uart4.
> I'll try to come up with a better patch.
You can call omap_serial_init_port() for each port from
board-zoom3.c instead of calling omap_serial_init().
See commit
Regards,
Tony
> Regards,
> Sergio
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of Aguirre, Sergio
> > Sent: Wednesday, February 24, 2010 1:31 AM
> > To: Tony Lindgren
> > Cc: linux-omap@vger.kernel.org; Sonasath, Moiz; Pandita, Vikram
> > Subject: [PATCH] omap2/3/4: serial: Half revert multiboot changes
> >
> > From 14bc4ee14ac5a3dab79d9292bf22ab0401879cd5 Mon Sep 17 00:00:00 2001
> > From: Sergio Aguirre <saaguirre@ti.com>
> > Date: Wed, 24 Feb 2010 01:15:55 -0600
> > Subject: [PATCH] omap2/3/4: serial: Half revert multiboot changes
> >
> > The patch named:
> > "omap2/3/4: Fix mach-omap2/serial.c for multiboot"
> >
> > Which added UART4 init also for 36xx based boards, broke zoom3
> > booting. External UART must be correctly initialized already
> > by board-zoom-debugboard.c file, therefore the addition on UART4
> > initialization can't be done blindly (i.e. board agnostic)
> >
> > This patch removes the 36xx uart4 init for the above reason.
> >
> > Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
> > ---
> > arch/arm/mach-omap2/serial.c | 10 ++--------
> > 1 files changed, 2 insertions(+), 8 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> > index b79bc89..fe3122b 100644
> > --- a/arch/arm/mach-omap2/serial.c
> > +++ b/arch/arm/mach-omap2/serial.c
> > @@ -115,7 +115,6 @@ static struct plat_serial8250_port
> > serial_platform_data2[] = {
> > }
> > };
> >
> > -#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4)
> > static struct plat_serial8250_port serial_platform_data3[] = {
> > {
> > .irq = 70,
> > @@ -132,11 +131,6 @@ static inline void omap2_set_globals_uart4(struct
> > omap_globals *omap2_globals)
> > {
> > serial_platform_data3[0].mapbase = omap2_globals->uart4_phys;
> > }
> > -#else
> > -static inline void omap2_set_globals_uart4(struct omap_globals
> > *omap2_globals)
> > -{
> > -}
> > -#endif
> >
> > void __init omap2_set_globals_uart(struct omap_globals *omap2_globals)
> > {
> > @@ -597,7 +591,7 @@ static struct omap_uart_state omap_uart[] = {
> > },
> > },
> > },
> > -#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4)
> > +#ifdef CONFIG_ARCH_OMAP4
> > {
> > .pdev = {
> > .name = "serial8250",
> > @@ -764,7 +758,7 @@ void __init omap_serial_init(void)
> > {
> > int i, nr_ports;
> >
> > - if (!(cpu_is_omap3630() || cpu_is_omap4430()))
> > + if (!cpu_is_omap4430())
> > nr_ports = 3;
> > else
> > nr_ports = ARRAY_SIZE(omap_uart);
> > --
> > 1.6.3.3
>
next prev parent reply other threads:[~2010-02-24 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 7:30 [PATCH] omap2/3/4: serial: Half revert multiboot changes Aguirre, Sergio
2010-02-24 7:40 ` Aguirre, Sergio
2010-02-24 16:21 ` Tony Lindgren [this message]
2010-02-25 3:07 ` Aguirre, Sergio
2010-02-25 18:55 ` Tony Lindgren
2010-02-25 20:36 ` Aguirre, Sergio
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=20100224162129.GO28173@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=m-sonasath@ti.com \
--cc=saaguirre@ti.com \
--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 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.