On 06/13/2014 10:55 AM, Tony Lindgren wrote: > * Roger Quadros <rog...@ti.com> [140611 01:59]: >> Move the code that puts the onenand in synchronous mode >> into the appropriate place i.e. drivers/mtd/onenand/omap2.c. >> >> Make use of omap_gpmc_get_clk_period() and omap_gpmc_retime() >> to calculate the necessary timings and configure the GPMC >> parent's timings. > > Ideally we would just use the drivers/mtd/onenand/generic.c > and get rid of drivers/mtd/onenand/omap2.c. We still need > the bus glue, which should probably be in drivers/memory? >
But what about the runtime synchronous timing calculations onenand/omap2.c? There is also OMAP2 and OMAP3 specific dma handling done there, which should probably be done generically using dmaengine. cheers, -roger -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
