From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH 4/4] ARM: tegra: fix Venice2 VQMMC regulators Date: Wed, 16 Apr 2014 10:19:29 -0600 Message-ID: <534EAD91.90704@wwwdotorg.org> References: <1397526163-20126-1-git-send-email-abrestic@chromium.org> <1397526163-20126-5-git-send-email-abrestic@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from avon.wwwdotorg.org ([70.85.31.133]:44537 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754924AbaDPQTd (ORCPT ); Wed, 16 Apr 2014 12:19:33 -0400 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Andrew Bresticker , Thierry Reding , Chris Ball , Ulf Hansson Cc: "linux-mmc@vger.kernel.org" , "linux-tegra@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" On 04/15/2014 06:29 PM, Andrew Bresticker wrote: >> sdhci@0,700b0600 { >> status = "okay"; >> bus-width = <8>; >> + vqmmc-supply = <&vddio_1v8>; > > It turns out this bit isn't needed as the initialization failures are > instead due to +3V3_RUN toggling, which Stephen has fixed: > http://patchwork.ozlabs.org/patch/339386/ Indeed, if I apply patches 1, 2, and 4 from this series, revert the hunk above, apply my Venice2 regulator patch, and finally apply your AS3722 regulator GPIO patch, then everything works fine for me:-) From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Wed, 16 Apr 2014 10:19:29 -0600 Subject: [PATCH 4/4] ARM: tegra: fix Venice2 VQMMC regulators In-Reply-To: References: <1397526163-20126-1-git-send-email-abrestic@chromium.org> <1397526163-20126-5-git-send-email-abrestic@chromium.org> Message-ID: <534EAD91.90704@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/15/2014 06:29 PM, Andrew Bresticker wrote: >> sdhci at 0,700b0600 { >> status = "okay"; >> bus-width = <8>; >> + vqmmc-supply = <&vddio_1v8>; > > It turns out this bit isn't needed as the initialization failures are > instead due to +3V3_RUN toggling, which Stephen has fixed: > http://patchwork.ozlabs.org/patch/339386/ Indeed, if I apply patches 1, 2, and 4 from this series, revert the hunk above, apply my Venice2 regulator patch, and finally apply your AS3722 regulator GPIO patch, then everything works fine for me:-)