Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762899AbZLLA67 (ORCPT ); Fri, 11 Dec 2009 19:58:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759163AbZLLA6x (ORCPT ); Fri, 11 Dec 2009 19:58:53 -0500 Received: from buzzloop.caiaq.de ([212.112.241.133]:54021 "EHLO buzzloop.caiaq.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756445AbZLLA6w (ORCPT ); Fri, 11 Dec 2009 19:58:52 -0500 Date: Sat, 12 Dec 2009 08:58:54 +0800 From: Daniel Mack To: Adrian Hunter Cc: Matt Fleming , David Brownell , Eric Miao , Linus Walleij , "Lavinen Jarkko (Nokia-D/Helsinki)" , Mark Brown , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "madhu.cr@ti.com >> Madhusudhan Chikkature" , Cliff Brake , Russell King , Pierre Ossman , Robert Jarzmik , Andrew Morton , "linux-arm-kernel@lists.infradead.org" , Liam Girdwood Subject: Re: [PATCH] mmc: move regulator handling to core Message-ID: <20091212005854.GV28375@buzzloop.caiaq.de> References: <1259844390-10541-1-git-send-email-daniel@caiaq.de> <4B17CADB.1070406@nokia.com> <20091203192044.GJ14091@buzzloop.caiaq.de> <4B181BB4.1020800@nokia.com> <20091204115805.GS14091@buzzloop.caiaq.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091204115805.GS14091@buzzloop.caiaq.de> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1584 Lines: 39 On Fri, Dec 04, 2009 at 12:58:05PM +0100, Daniel Mack wrote: > > >On Thu, Dec 03, 2009 at 04:27:39PM +0200, Adrian Hunter wrote: > > > >>What about arch/arm/mach-omap2/mmc-twl4030.c ? > > > > > >Argh, missed that one. And this particular case doesn't fit to my > > >modifications. I don't know the code well ... We would need to > > >have a struct mmc_host * in all the functions there calling > > >mmc_regulator_{set,get}_ocr. Any idea how to resolve that? > > > > > > > Pass it down from the omap_hsmmc driver. > > It's not that easy, unfortunately, because this code does not conform to > all the other mmc host drivers in tree. > > I don't understand why things are done the way it is currently > implemented. Why isn't there a mmc_host for each slot, and why is a > regulator reference acquired for each slot, and not once for the whole > device? > > Even with the default 'vcc' supply factored out to the mmc core, the > 'vmmc_aux' regulator would still need some extra attention, but I would > also do that from the omap_hsmmc driver rather than in the plaform > support code. > > Moving the regulator handling to the mmc core would require a major > cleanup to all this code, but I don't have such hardware to test my > modifications. Can anyone help here? Can anyone of the OMAP people help sort this out? Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/