Omar Ramirez Luna <omar.luna@xxxxxxxxxx> writes: > On 11 July 2012 12:07, Kevin Hilman <khilman@xxxxxx> wrote: > ... >>> [ 2.311004] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk >>> [ 2.317382] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62 >>> [ 2.325256] omap_hsmmc omap_hsmmc.1: Failed to get debounce clk >>> [ 2.331512] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48 >> >> These are normal because DMA engine is not compiled in with >> omap2plus_defconfig. MMC wont' work unless you build in DMA engine, but >> that doesn't matter for trying to figure out your problem. > > Hijacking this thread a little bit... > > It looks like a dependency is missing in Kconfig then, as this also > fails to boot if the file system is in MMC. As you pointed out > CONFIG_DMADEVICES and CONFIG_DMA_OMAP is needed to boot in this case. > I'm using a Panda 4460. Yes, the drivers that have been converted to DMA engine should probably 'select DMADEVICES' and 'select DMA_OMAP' since they will now depend on DMA engine. Kevin -- 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
