Hi Tony, On Wed, Apr 25, 2012 at 22:14:25, Tony Lindgren wrote: > > Once driver is acceptable, platform code for other peripherals > > connected via GPMC would be adapted to make use of GPMC driver. And > > then the board modifications. But before that HWMOD entry has to be > > populated for respective SoC(s ?). > > No, we can't do it this way, it breaks things. We need to first > convert everything to use the new GPMC driver, then move it. Sorry, my statements were not clear, I meant once driver is acceptable & still living in mach-omap2, platform code dealing with peripherals on gpmc would be adapted to make use of gpmc driver. Moving driver to new location is only planned as a separate commit after, before mentioned changes. Hope with this clarification we are on same track. > > > Now DESTINATION FOR THIS DRIVER has to be decided. Original plan was > > to consider GPMC as MFD. The peripheral(s) connected to GPMC being > > considered childs of MFD. > > Let's not put it into MFD. This is a bus driver. But that > decision can wait as we cleary have quite a few things to convert > first under arch/arm/mach-omap2. > > > Various options that could be seen so far on where this driver can go, > > 1. mfd > > 2. misc > > 3. drivers/platform/arm/ (create an new one?) > > 4. memory (create a new one ?) > > It's a parallel bus driver, not memory not misc, not MFD. Greg suggested to send gpmc driver to new memory folder. In the next version, gpmc driver would still be in mach-omap2, moving to new location can be done later. 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
