From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Thu, 1 Oct 2015 10:33:25 +0100 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: <20151001093325.GU21513@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Sep 24, 2015 at 04:37:56PM -0700, Tony Lindgren wrote: > * 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. It's still broken and untestable. We're 8 days off it being a full month worth of failed testing for OMAP3 and OMAP4 platforms. I think OMAP and MMC people need to do a post-mortem and work out why this happened, and how to stop it happening again in the future. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.