Hi, On Mon, Nov 12, 2012 at 12:38:37AM +0200, Constantine Shulyupin wrote: > 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. before getting rid of platform_data, we need to switch over to proper frameworks for muxing, clock, etc. In case of EHCI, pinctrl migration is currently under development by Keshava (in Cc). After that we need to take a look at platform and see if there are any function pointers in there, if there are, those need to be removed. > How to perform board specific initializations? > Can omap4_ehci_init be converted to probe function of new platform > driver omap4_ehci? yeah, that function is actually wrong. First, that GPIO pin belongs to the HUB driver, not the EHCI driver. Second, those clocks belong to the PHY, not EHCI either. Before those details are cleaned up, we will always have hacky solutions which will break in one way or another. When those cleanups are done, conversion to FDT is not a problem at all. -- balbi
Attachment:
signature.asc
Description: Digital signature
