Hi Paul, On Thu, May 10, 2012 at 11:33:44, Mohammed, Afzal wrote: > Hi Paul, > > On Tue, May 08, 2012 at 21:02:33, Paul Walmsley wrote: > > > > Major reason was that there are some boards that rely on bootloader > > > settings, eg. kernel does not do any setting for smsc911x. I did not > > > want to break those, at least it causes problem with omap3evm, see below > > > > But this is the whole point. The Linux GPMC driver and integration code > > should be setting up the GPMC registers based on board file and/or DT > > data, before the kernel touches any GPMC devices. > > > > We don't want to rely on the bootloader settings unless we absolutely have > > no other choice. Otherwise, the stability of the kernel could easily be > > impacted by the bootloader's GPMC timings and other register settings, and > > we want to minimize those potential sources of variation. > > > > So if we absolutely have no choice than to keep HWMOD_INIT_NO_RESET here, > > which doesn't sound like the case so far, we need to understand exactly > > why this is so. > > There are 14 out of 20 boards partially or fully relying on bootloader > settings. I will try to do configuration for smsc911x in Kernel itself, > this is the only one that can be tested from my side (on omap3evm), but > there are other peripherals like NOR, quaduart, onenand-flash (different > from omap-onenand), then smc91x (timings are not set from kernel for > sdp boards), these would affect 7 boards of both omap2 & omap3. To > get configuration done from Kernel properly without having these boards > is too tough for me. > > So I request you to keep HWMOD_INIT_NO_RESET (I will add configuration > for smsc911x), please let me know your comments. ping Regards Afzal -- 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
