> +static void __init omap4_panda_init(void)
> +{
> + int status;
> +
> + omap4_panda_i2c_init();
> + omap_serial_init();
> + omap4_twl6030_hsmmc_init(mmc);
> + /* OMAP4 Panda 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);
> +}
Dave,
I think this should be resolved by now - the OMAP4 MUSB support went
through linux-usb for .35-rc1. So it should be safe to call
usb_musb_init() unconditionally.
(Not actually tested by me yet. I'll try and do this tomorrow).
- Anand
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
