Hello all, I'm not exactly sure where to ask this, but I figured it would be on a mailing list that is linux specific, with a slight bias towards the OMAP:
I have an OMAP3530 mated to an FPGA over the GPMC interface found on that chip. I have an interrupt controller on the FPGA (and mapped into virtual IRQs in Linux through irqchip and chained handlers) and a few UARTs in it as well - the UART is specifically chosen to be 16550 compatible so that it can directly be mapped as a platform device into the 8250 serial platform driver. This way, I avoid having to write a serial driver, and it is directly compatible with that in Linux. The FPGA currently is programmed by a separate device on boot, and that process can take up to 20 seconds - hence, the interrupt layer and serial driver in Linux cannot really be loaded until the FPGA has completed boot. At the same time, I do not want to hold-off booting Linux till the FPGA is alive. What is the correct solution to this? Should I just load the interrupt and serial drivers anyways (and not use them till the FPGA is up) or should I defer loading them? If the latter is a better idea, how do I do a deferred hotplug-style serial device connection? Can platform_device_register happen much later in the boot lifecycle? Any ideas are much appreciated! Thanks, Jerry Johns Design Engineer Nuvation Research Corp - Canada Tel: (519) 746-2304 ext. 221 www.nuvation.com -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
