linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Anders, David" <x0132446@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Add OMAP4 Panda support
Date: Mon, 17 May 2010 20:36:36 -0700	[thread overview]
Message-ID: <20100518033636.GL5818@atomide.com> (raw)
In-Reply-To: <7B4574D56E4ADF438756313E9A172A8799C0D3C6@dlee01.ent.ti.com>

* Anders, David <x0132446@ti.com> [100517 13:13]:
> Add initial support for the OMAP4430 based Panda board.
> 
> Signed-off-by: David Anders <x0132446@ti.com>

<snip>

> +
> +static void __init omap4_panda_init_irq(void)
> +{
> +       omap2_init_common_hw(NULL, NULL);
> +#ifdef CONFIG_OMAP_32K_TIMER
> +       omap2_gp_clockevent_set_gptimer(1);
> +#endif
> +       gic_init_irq();
> +       omap_gpio_init();
> +}
> +
> +static struct omap_musb_board_data musb_board_data = {
> +       .interface_type         = MUSB_INTERFACE_UTMI,
> +       .mode                   = MUSB_PERIPHERAL,
> +       .power                  = 100,
> +};
> +
> +static void __init omap4_panda_init(void)
> +{
> +       omap_serial_init();
> +       /* OMAP4 SDP uses internal transceiver so register nop transceiver */
> +       usb_nop_xceiv_register();
> +       /* FIXME: allow multi-omap to boot until musb is updated for omap4 */
> +       if (!cpu_is_omap44xx())
> +               usb_musb_init(&musb_board_data);
> +
> +}
> +
> +static void __init omap4_panda_map_io(void)
> +{
> +       omap2_set_globals_443x();
> +       omap44xx_map_common_io();
> +}
> +
> +MACHINE_START(OMAP4_PANDA, "OMAP4 Panda board")
> +       /* Maintainer: David Anders - Texas Instruments Inc */
> +       .phys_io        = 0x48000000,
> +       .io_pg_offst    = ((0xfa000000) >> 18) & 0xfffc,
> +       .boot_params    = 0x80000100,
> +       .map_io         = omap4_panda_map_io,
> +       .init_irq       = omap4_panda_init_irq,
> +       .init_machine   = omap4_panda_init,
> +       .timer          = &omap_timer,
> +MACHINE_END

Cool, good to see this posted early.

However, looks like this can wait until the next merge window
though as it was posted so late.

Regards,

Tony

  reply	other threads:[~2010-05-18  3:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 20:18 [PATCH] Add OMAP4 Panda support Anders, David
2010-05-18  3:36 ` Tony Lindgren [this message]
2010-06-18  6:58   ` Felipe Balbi
2010-06-18  8:17     ` Tony Lindgren
     [not found]     ` <64809C8C-FAB5-4540-A47A-B0967B5C3B7F@mac.com>
2010-06-18 10:01       ` Felipe Balbi
2010-06-18 14:32 ` Kevin Hilman
2010-06-18 14:57   ` Anders, David
2010-06-18 15:13     ` Kevin Hilman
2010-06-18 15:56       ` Anders, David
2010-06-18 16:06         ` Kevin Hilman
2010-06-18 15:26   ` Gadiyar, Anand
  -- strict thread matches above, loose matches on Subject: below --
2010-06-24 19:33 [PATCH] Add OMAP4 Panda Support David Anders
2010-06-25  1:29 ` Gadiyar, Anand
2010-06-28 17:47   ` Anders, David
2010-07-05 11:51     ` Tony Lindgren
2010-07-06 16:05       ` Anders, David

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=20100518033636.GL5818@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=x0132446@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).