From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yegor Yefremov Subject: Re: am3517: geting MMC working Date: Thu, 19 Jul 2012 08:55:56 +0200 Message-ID: <5007AF7C.1010902@visionsystems.de> References: <5007A838.3040309@visionsystems.de> Reply-To: yegor_sub1@visionsystems.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ns.vscom.de ([62.145.30.242]:54815 "EHLO mail.visionsystems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750917Ab2GSG4L (ORCPT ); Thu, 19 Jul 2012 02:56:11 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Shilimkar, Santosh" Cc: "linux-omap@vger.kernel.org" , "Mark A. Greer" , "Porter, Matt" Am 19.07.2012 08:34, schrieb Shilimkar, Santosh: > On Thu, Jul 19, 2012 at 11:54 AM, Yegor Yefremov > 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