linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mmci: Improve runtime PM support
Date: Mon, 24 Oct 2011 10:56:38 +0100	[thread overview]
Message-ID: <20111024095638.GJ9893@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACRpkdY6rzYsYQW+GACL6Ux8o=Eo-3wn62O0YZxJZ=F2WbE4DQ@mail.gmail.com>

On Mon, Oct 24, 2011 at 11:54:00AM +0200, Linus Walleij wrote:
> On Mon, Oct 24, 2011 at 11:36 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Sun, Oct 23, 2011 at 02:31:39AM +0200, Sebastian Rasmussen wrote:
> >> I guess the patch would appeal more to Russell if mmci_runtime_suspend()
> >> only cleared MCIMask0/SDI_MASK0 and MCIClock/SDI_CLKCR and left
> >> MCIPower/SDI_PWR unchanged. It may be the case that the signal direction
> >> bits need to be cleared for the ST-Ericsson PL180, but I haven't yet verified
> >> this on my Snowball dev board yet.
> >
> > There's also the issue that the specs call for the clock to run after
> > a command has completed for a certain number of cycles, and that the
> > clock must continue to run until the card reports not-busy after a
> > programming or erase cycle has completed - that can be long after the
> > previous command has 'completed'.
> 
> It's 8 cycles on MCLK required.

_Plus_ keeping the clock running while the card is signalling busy.

If you don't clock the card while its signalling busy, it will never
go non-busy (the data line becomes frozen.)

  reply	other threads:[~2011-10-24  9:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 15:25 [PATCH] mmc: mmci: Improve runtime PM support Ulf Hansson
2011-10-21 17:36 ` Russell King - ARM Linux
     [not found]   ` <CAKnu2MrOriMzJH9NcwUivWa0cinASa6wrRf4a69si4WUs-aTrQ@mail.gmail.com>
2011-10-23  0:31     ` Sebastian Rasmussen
2011-10-24  8:05       ` Ulf Hansson
2011-10-24  9:04         ` Russell King - ARM Linux
2011-10-24  9:36           ` Ulf Hansson
2011-10-24  9:42             ` Russell King - ARM Linux
2011-10-24 10:06               ` Ulf Hansson
2011-10-24 10:14                 ` Russell King - ARM Linux
2011-10-24 11:48                   ` Ulf Hansson
2011-10-24 12:18                     ` Linus Walleij
2011-10-24 15:25                       ` Ulf Hansson
2011-10-24 15:34                         ` Ulf Hansson
2011-10-25  7:12                         ` Linus Walleij
2011-10-25  7:39                           ` Ulf Hansson
2011-10-24  9:11         ` Sebastian Rasmussen
2011-10-24  9:14         ` Linus Walleij
2011-10-24  9:36       ` Russell King - ARM Linux
2011-10-24  9:54         ` Linus Walleij
2011-10-24  9:56           ` Russell King - ARM Linux [this message]
2011-10-24 10:17             ` Ulf Hansson
2011-10-24 11:49               ` Linus Walleij
2011-10-25  8:05             ` Adrian Hunter
2011-10-25  8:53               ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111024095638.GJ9893@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).