* Afzal Mohammed <afzal@xxxxxx> [120405 09:06]: > Hi, > > GPMC driver conversion series. NAND and smsc911x ethernet device has > been adapted to use GPMC driver. > > Patches has been generated over linux-omap/master, HEAD > 33fc21e Linux-omap rebuilt: Updated to v3.4-rc1, merged in most of pending branches > As OMAP3EVM does not boot linux-omap/master, merge commit, > 58adb29 Merge branch 'io_chain_devel_3.4' of git://git.pwsan.com/linux-2.6 into prm > has to be reverted to get OMAP3EVM boot. > Last patch (with subject prefix TMP - 9/9) is for testing. > > 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. > 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. Cheers, Tony -- 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
