Hi Jon, On Tue, Jun 12, 2012 at 23:00:48, Hunter, Jon wrote: > On 06/12/2012 01:16 AM, Mohammed, Afzal wrote: > > With the existing code, set_async was done as part of set_sync, hence > > requiring GPMC to be configured twice after driver takes control, with > > your suggestion too, GPMC would have to be configured twice. > > I am just suggesting that you place the call to set_async_mode in the > gpmc_onenand_setup() instead of the gpmc_onenand_init() and remove the > calls from set_sync (like you have done). So I don't see that these > would configure the GPMC twice. As gpmc_onenand_setup is a callback by onenand driver, we would have lost the opportunity to configure onenand before driver is probed. This would cause requirement of double GPMC configuring and we lost the opportunity to configure GPMC before driver is probed. And the first step for onenand configuration is always to set it to async mode (with the way it is done now), so it seems reasonable to rely on normal GPMC configuration for async & then do reconfigure for sync. 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
