Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756310AbZLCPJz (ORCPT ); Thu, 3 Dec 2009 10:09:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756321AbZLCPJy (ORCPT ); Thu, 3 Dec 2009 10:09:54 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:38984 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756319AbZLCPJx (ORCPT ); Thu, 3 Dec 2009 10:09:53 -0500 Date: Thu, 3 Dec 2009 15:09:55 +0000 From: Mark Brown To: Russell King - ARM Linux Cc: Daniel Mack , Matt Fleming , David Brownell , Eric Miao , Linus Walleij , Jarkko Lavinen , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Cliff Brake , Pierre Ossman , Liam Girdwood , Robert Jarzmik , Andrew Morton , linux-arm-kernel@lists.infradead.org, Adrian Hunter Subject: Re: [PATCH] mmc: move regulator handling to core Message-ID: <20091203150955.GA10297@rakim.wolfsonmicro.main> References: <1259844390-10541-1-git-send-email-daniel@caiaq.de> <20091203130627.GA31254@rakim.wolfsonmicro.main> <20091203131423.GV14091@buzzloop.caiaq.de> <20091203132241.GB31533@rakim.wolfsonmicro.main> <20091203145825.GA26651@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091203145825.GA26651@n2100.arm.linux.org.uk> X-Cookie: When among apes, one must play the ape. 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: 1139 Lines: 23 On Thu, Dec 03, 2009 at 02:58:25PM +0000, Russell King - ARM Linux wrote: > On Thu, Dec 03, 2009 at 01:22:41PM +0000, Mark Brown wrote: > > without power control). This goes back to the thing about using > > regulator_get_exclusive(), the message given was that the MMC drivers > > really needed to be able to guarantee that the power would be removed > > when that was requested. > If you take some cards through a series of steps and they stop responding, > it's normally because you've caused their internal state machine to > transition to "invalid" mode. > Further commands are ignored. The only recovery is to power cycle them. I assume that this is something it's desirable to be able to do in the face of poor hardware rather than something that the Linux MMC stack is actively using in normal operation (modulo issues with the general quality of implementation of MMC hardware)? -- 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/