From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe Balbi Subject: Re: [patch 2.6.29-rc7-omap-git] Overo: MMC regulator configuration Date: Wed, 11 Mar 2009 21:33:47 +0200 Message-ID: <20090311193347.GC19730@gandalf> References: <200903111158.29860.david-b@pacbell.net> Reply-To: me@felipebalbi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from ns1.siteground211.com ([209.62.36.12]:42579 "EHLO serv01.siteground211.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750769AbZCKTdy (ORCPT ); Wed, 11 Mar 2009 15:33:54 -0400 Content-Disposition: inline In-Reply-To: <200903111158.29860.david-b@pacbell.net> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: David Brownell Cc: OMAP , Steve Sakoman On Wed, Mar 11, 2009 at 10:58:29AM -0800, David Brownell wrote: > From: David Brownell > > This patch hooks up the twl4030 MMC1 regulator on Overo, > as well as the MMC1 card detect signal. The WLAN chip > connected to MMC2 on some board versions has a dedicated > regulator. > > Signed-off-by: David Brownell > --- > Patches still needed for LDP/Zoom and Pandora... with this patch I get: regulator: Unable to get requested regulator: vmmc_aux ------------[ cut here ]------------ WARNING: at drivers/regulator/core.c:1216 regulator_disable+0x64/0x90() unbalanced disables for supply mmci-omap-hs.0-vmmc Modules linked in: [] (dump_stack+0x0/0x14) from [] (warn_slowpath+0x6c/0x88) [] (warn_slowpath+0x0/0x88) from [] (regulator_disable+0x64/0x90) r3:cf9deae0 r2:c0425c79 r7:cfa16e00 r6:cfa06c38 r5:cfa16e00 r4:fffffffb [] (regulator_disable+0x0/0x90) from [] (mmc_regulator_set_ocr+0xb0/0xcc) r7:cfa16e00 r6:00000001 r5:00000000 r4:00000000 [] (mmc_regulator_set_ocr+0x0/0xcc) from [] (twl_mmc1_set_power+0xc0/0xec) r7:cfa93538 r6:00000000 r5:00000000 r4:c04a5b58 [] (twl_mmc1_set_power+0x0/0xec) from [] (omap_mmc_set_ios+0x54/0x314) r7:cfa93538 r6:cfa935c0 r5:cfa93400 r4:cf9a93c0 [] (omap_mmc_set_ios+0x0/0x314) from [] (mmc_power_off+0x90/0x9c) r7:00000000 r6:00000000 r5:cfa93400 r4:00000000 [] (mmc_power_off+0x0/0x9c) from [] (mmc_start_host+0x14/0x24) r5:00000000 r4:cfa93400 [] (mmc_start_host+0x0/0x24) from [] (mmc_add_host+0x64/0x70) r5:00000000 r4:cfa93400 [] (mmc_add_host+0x0/0x70) from [] (omap_mmc_probe+0x464/0x614) r5:cfa935c0 r4:cfa93470 [] (omap_mmc_probe+0x0/0x614) from [] (platform_drv_probe+0x20/0x24) [] (platform_drv_probe+0x0/0x24) from [] (driver_probe_device+0xd4/0x180) [] (driver_probe_device+0x0/0x180) from [] (__driver_attach+0x68/0x8c) r7:cfa15120 r6:c0499e34 r5:cfa06290 r4:cfa06208 [] (__driver_attach+0x0/0x8c) from [] (bus_for_each_dev+0x4c/0x80) r7:cfa15120 r6:c0499e34 r5:c01d6e00 r4:00000000 [] (bus_for_each_dev+0x0/0x80) from [] (driver_attach+0x20/0x28) r6:c0499e34 r5:00000000 r4:00000000 [] (driver_attach+0x0/0x28) from [] (bus_add_driver+0xa4/0x20c) [] (bus_add_driver+0x0/0x20c) from [] (driver_register+0x98/0x120) r8:00000000 r7:c002182c r6:c0499e34 r5:00000000 r4:c0028a58 [] (driver_register+0x0/0x120) from [] (platform_driver_register+0x6c/0x88) r9:00000000 r8:00000000 r7:c002182c r6:00000000 r5:00000000 r4:c0028a58 [] (platform_driver_register+0x0/0x88) from [] (omap_mmc_init+0x14/0x1c) [] (omap_mmc_init+0x0/0x1c) from [] (__exception_text_end+0x5c/0x19c) [] (__exception_text_end+0x0/0x19c) from [] (kernel_init+0x80/0xf4) r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:c0028a58 [] (kernel_init+0x0/0xf4) from [] (do_exit+0x0/0x6a4) r4:00000000 ---[ end trace e00c52255ce89b8f ]--- mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock regulator: Unable to get requested regulator: vmmc does this depend on any patch dave ? Using current omap HEAD. -- balbi