Am 19.07.2012 08:34, schrieb Shilimkar, Santosh: > On Thu, Jul 19, 2012 at 11:54 AM, Yegor Yefremov > <[email protected]> wrote: >> What patches do I need to get MMC working with linux-omap master? >> >> omap_hsmmc omap_hsmmc.0: Failed to get debounce clk >> omap-dma-engine omap-dma-engine: allocating channel for 62 >> omap-dma-engine omap-dma-engine: allocating channel for 61 >> omap_hsmmc omap_hsmmc.1: Failed to get debounce clk >> omap-dma-engine omap-dma-engine: allocating channel for 48 >> omap-dma-engine omap-dma-engine: allocating channel for 47 >> >> I searched for this issue and saw some patches for common clock framework >> that were scheduled for 3.6, but I'm not sure it's enough or weather they >> are already incorporated in linux-omap. >> > I guess you need [1] to get around the issue. > > [1] http://www.spinics.net/lists/linux-omap/msg73965.html
though I haven't applied this patch I have DMA activated (CONFIG_DMADEVICES and CONFIG_DMA_OMAP). Found in some other thread [1]. As far as I can tell, debounce clk is the problem. [1] http://www.spinics.net/lists/linux-omap/msg73703.html Yegor -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
