From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: All OMAP platforms: MMC is broken Date: Thu, 24 Sep 2015 18:13:34 -0700 Message-ID: <20150925011334.GP23801@atomide.com> References: <20150924090048.GA21626@n2100.arm.linux.org.uk> <20150924233756.GN23801@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from muru.com ([72.249.23.125]:53978 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752261AbbIYBNi (ORCPT ); Thu, 24 Sep 2015 21:13:38 -0400 Content-Disposition: inline In-Reply-To: <20150924233756.GN23801@atomide.com> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Russell King - ARM Linux Cc: Ulf Hansson , linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Kishon Vijay Abraham I * Tony Lindgren [150924 16:42]: > * Russell King - ARM Linux [150924 02:04]: > > Nightly testing has revealed that both the OMAP3430 LDP and the OMAP4430 > > SDP fail to boot due to lack of working MMC. Both platforms fail to > > find their rootfs, which is on a SD card. > > > > The breakage occurred somewhere between trees of September 9th (commit > > 4e4adb2f4628) and September 12th (commit b0a1ea51bda4), so during the > > merge window. > > Yes sorry things got messed up in multiple ways :( I've summarized > the mess here earlier: > > http://article.gmane.org/gmane.linux.kernel.mmc/33911 > > And today commit b9c93646fd5c ("regulator: pbias: program pbias register > offset in pbias driver") hit mainline so I'll send a pull request for > the related dts change. Kishon, while testing I noticed there are still at least two issues remaining that seem to need fixing in the MMC driver: 1. The legacy booting without device tree does not probe MMC at all on omap3 2. I'm getting the regulator warning on omap4 duovero Anyways, I'm sending a pull request for the fixes so far as that gets MMC working again for most platforms. Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 24 Sep 2015 18:13:34 -0700 Subject: All OMAP platforms: MMC is broken In-Reply-To: <20150924233756.GN23801@atomide.com> References: <20150924090048.GA21626@n2100.arm.linux.org.uk> <20150924233756.GN23801@atomide.com> Message-ID: <20150925011334.GP23801@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Tony Lindgren [150924 16:42]: > * Russell King - ARM Linux [150924 02:04]: > > Nightly testing has revealed that both the OMAP3430 LDP and the OMAP4430 > > SDP fail to boot due to lack of working MMC. Both platforms fail to > > find their rootfs, which is on a SD card. > > > > The breakage occurred somewhere between trees of September 9th (commit > > 4e4adb2f4628) and September 12th (commit b0a1ea51bda4), so during the > > merge window. > > Yes sorry things got messed up in multiple ways :( I've summarized > the mess here earlier: > > http://article.gmane.org/gmane.linux.kernel.mmc/33911 > > And today commit b9c93646fd5c ("regulator: pbias: program pbias register > offset in pbias driver") hit mainline so I'll send a pull request for > the related dts change. Kishon, while testing I noticed there are still at least two issues remaining that seem to need fixing in the MMC driver: 1. The legacy booting without device tree does not probe MMC at all on omap3 2. I'm getting the regulator warning on omap4 duovero Anyways, I'm sending a pull request for the fixes so far as that gets MMC working again for most platforms. Regards, Tony