On Tue, Jul 17, 2012 at 12:33 PM, Javier Martinez Canillas <javier@xxxxxxxxxxxx> wrote: > The OMAP MMC and OMAP High Speed MMC hosts now use entirely the DMA > engine API instead of the previous private DMA API implementation. > > So, if the kernel is built with support for any of these hosts but it > doesn't support DMA devices nor OMAP DMA support, it fails when trying > to obtain a DMA channel which leads to the following error on an OMAP3 > IGEPv2 Rev.C board (and probably on most OMAP boards with MMC support): > > [ 2.199981] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48 > [ 2.215087] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62 > > selecting automatically CONFIG_DMADEVICES and CONFIG_DMA_OMAP solves it. > > While being there, also update drivers/spi/spi-omap2-mcspi which has been > ported to DMA engine API too. > > Signed-off-by: Javier Martinez Canillas <javier@xxxxxxxxxxxx> > --- > Looks like this patch should go to Russell's tree where rest of the OMAP DMA engine patches are queued. For the patch itself, Acked-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
