* Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120418 13:28]: > On Wed, Apr 18, 2012 at 01:02:15PM -0700, Tony Lindgren wrote: > > The scatterlist entries are separate DMA requests on omap1, there's no > > chaining support in the DMA hardware on omap1. So yes, it's for every > > scatterlist entry on omap1. > > There's no direct scatterlist support on OMAP2 either (omap_hsmmc _used_ > to do each scatterlist entry separately too). The DMA engine driver > does the same, but will walk the scatterlist internally rather than the > driver having to do it. OK > I'd like to have the same thing happen on OMAP1 as well (it's actually > quite simple to do) and it means that this DMA engine implementation > detail is (correctly) hidden from the drivers - provided there's no > dependencies on each individual scatterlist entry back to the peripheral > driver. That would be nice. If the DMA engine driver can't dynamically adjust the frame size for each SG entry, then maybe we can work around that by not doing DMA for entries that are below the frame sizes? 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
