[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Nov 2012 00:38:37 +0200
From: Constantine Shulyupin <const@...elinux.com>
To: Felipe Balbi <balbi@...com>, Tony Lindgren <tony@...mide.com>,
Santosh Shilimkar <santosh.shilimkar@...com>, nsekhar@...com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-omap@...r.kernel.org, linux@....linux.org.uk,
tim.bird@...sony.com, pandaboard@...glegroups.com
Subject: Porting board initialization for fdt
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists