All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "Christensen, Mikkel" <mlc@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] OMAP3:zoom2: Add support for OMAP3 Zoom2 board
Date: Wed, 20 May 2009 14:12:36 -0700	[thread overview]
Message-ID: <20090520211235.GI8308@atomide.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F50968B4@dbde02.ent.ti.com>

* Pandita, Vikram <vikram.pandita@ti.com> [090519 17:10]:
> Tony
> 
> >-----Original Message-----
> >From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of
> >Pandita, Vikram
> >Sent: Tuesday, May 19, 2009 7:01 PM
> >To: Tony Lindgren
> >Cc: Christensen, Mikkel; linux-omap@vger.kernel.org
> >Subject: RE: [PATCH v3 1/3] OMAP3:zoom2: Add support for OMAP3 Zoom2 board
> >
> >
> >
> <snip>
> >>
> >>Well you still cannot have it as a late_initcall(), you should just call the
> >>function from board-zoom2.c. Otherwise it will run for all the boards.
> 
> Way not execute the debug board function for other boards could be to put it under 
> #ifdef CONFIG_MACH_OMAP_ZOOM2 
> 
> static int __init omap_zoom2_debugboard_init(void)
> {
> #ifdef CONFIG_MACH_OMAP_ZOOM2
>         if (!omap_zoom2_debugboard_detect())
>                 return 0;
> 
>         zoom2_init_smsc911x();
>         zoom2_init_quaduart();
>         return platform_add_devices(zoom2_devices, ARRAY_SIZE(zoom2_devices));
> #endif
> }
> late_initcall(omap_zoom2_debugboard_init);
> 
> 
> The registration order of the UARTS with 8250 driver is all the reason we have to do this _initcall()

Hmm, OK. That sounds like a bug that's from some older code. We should probably
just do the platform_device_register in omap_serial_init(), then you can call
your zoom_debug_init() after omap_serial_init().

Care to do a separate patch to get rid of omap_init in mach-omap2/serial.c, and do
the registration in omap_serial_init()?

Regards,

Tony

> 
> 
> >
> >The problem is that serial.c: platform_device_register() for UART1/2/3 happens as arch_init().
> >
> >We want that Quard/Dbg-board Uart console to appear as UART4(ttyS3) and so the
> >platform_device_register() has to happen after the arch_init() call from serial.c
> >
> >If we put the dbg-board init in .init_machine   = omap_zoom2_init() function, then this gets called
> >first before the serial.c:arch_init() and assigns ttyS0(UART0) to the debug board uart.
> >
> >This is not what we want to do.
> >
> >
> >>
> >>Regards,
> >>
> >>Tony
> >>
> >
> >--
> >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
> 

  reply	other threads:[~2009-05-20 21:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 21:20 [PATCH v3 0/3] Support for OMAP3 Zoom2 board Mikkel Christensen
2009-05-15 21:20 ` [PATCH v3 1/3] OMAP3:zoom2: Add support " Mikkel Christensen
2009-05-15 21:20   ` [PATCH v3 2/3] OMAP3:zoom2: Defconfig for " Mikkel Christensen
2009-05-15 21:20     ` [PATCH v3 3/3] OMAP3:zoom2: Makefile and Kconfig " Mikkel Christensen
2009-05-18 21:22   ` [PATCH v3 1/3] OMAP3:zoom2: Add support for OMAP3 " Tony Lindgren
2009-05-18 21:30     ` Pandita, Vikram
2009-05-18 21:39       ` Tony Lindgren
2009-05-19  3:55         ` Pandita, Vikram
2009-05-19 16:29           ` Tony Lindgren
2009-05-19 23:48             ` Pandita, Vikram
2009-05-19 23:55               ` Tony Lindgren
2009-05-20  0:01                 ` Pandita, Vikram
2009-05-20  0:10                   ` Pandita, Vikram
2009-05-20 21:12                     ` Tony Lindgren [this message]
2009-05-20 21:15                       ` Pandita, Vikram
2009-05-15 22:34 ` [PATCH v3 0/3] Support " 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=20090520211235.GI8308@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mlc@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.