From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: PM/RTC 3.5-rc5: System suspends fails when not built with RTC? Date: Wed, 11 Jul 2012 14:29:27 -0700 Message-ID: <87wr2ahtqg.fsf@ti.com> References: <87zk77p3s5.fsf@ti.com> <87pq82kz0l.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog118.obsmtp.com ([74.125.149.244]:44592 "EHLO na3sys009aog118.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754347Ab2GKV32 (ORCPT ); Wed, 11 Jul 2012 17:29:28 -0400 Received: by yenq11 with SMTP id q11so1775518yen.2 for ; Wed, 11 Jul 2012 14:29:26 -0700 (PDT) In-Reply-To: (Omar Ramirez Luna's message of "Wed, 11 Jul 2012 15:52:00 -0500") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Omar Ramirez Luna Cc: Joe Woodward , "linux-omap@vger.kernel.org" Omar Ramirez Luna writes: > On 11 July 2012 12:07, Kevin Hilman 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