On Thu, Jul 19, 2012 at 12:25 PM, Yegor Yefremov <yegor_s...@visionsystems.de> wrote: > Am 19.07.2012 08:34, schrieb Shilimkar, Santosh: >> On Thu, Jul 19, 2012 at 11:54 AM, Yegor Yefremov >> <yegor_s...@visionsystems.de> 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. > Sorry. I miss-read the message.
Regards santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
