Porting board initialization for fdt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What is architecture and the best strategy to port board initialization to fdt?

Let's see for example omap4_ehci_init and usbhs_bdata @
arch/arm/mach-omap2/board-omap4panda.c.

How to perform board specific initializations?
Can omap4_ehci_init be converted to probe function of new platform
driver  omap4_ehci?
Where and how define GPIO, clock?
Should it be defined in of_dev_auxdata or in fdt?

Thanks

-- 
Constantine Shulyupin
http://www.MakeLinux.com/
Embedded Linux Systems
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux