From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: Possible regression with commit 52221610d Date: Tue, 16 Dec 2014 11:46:52 -0700 Message-ID: <54907E1C.10300@wwwdotorg.org> References: <54584260.8030602@nvidia.com> <545895B2.2000101@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from avon.wwwdotorg.org ([70.85.31.133]:38369 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751030AbaLPSqs (ORCPT ); Tue, 16 Dec 2014 13:46:48 -0500 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Tim Kryger , Bjorn Andersson Cc: Ulf Hansson , Alexandre Courbot , Sachin Kamat , linux-mmc , "linux-kernel@vger.kernel.org" , Alexandre Courbot On 12/14/2014 09:48 PM, Tim Kryger wrote: > On Sat, Dec 13, 2014 at 11:22 PM, Bjorn Andersson wrote: ... >> Or simply; what is vmmc (in the code) supposed to represent? > > Hi Bjorn, > > VMMC is the supply that delivers power out to the SD card itself (aka VDD). > > It is not the internal power rail/power domain of the host controller > within the SoC. I've seen this question come up quite a few times. Should Documentation/devicetree/bindings/mmc/mmc.txt document the vmmc/vqmmc regulators? I assume they're considered shared across all MMC/SDHCI controller bindings? Since that only covers DT, it might be nice to document vmmc-vs-vqmmc somewhere else too, such as right by the devm_regulator_get_optional() calls in mmc_regulator_get_supply() in drivers/mmc/core/core.c.