[PATCH 3/7] ARM: U300: set f_max to 24 MHz for MMCI
linus.walleij at stericsson.com
Wed Feb 24 16:25:37 EST 2010
OK I have now investigated this MMCI HW flow control mentioned
earlier (Dan, this may be outside your interests, sorry in that
> > if (host->hw_designer == AMBA_VENDOR_ST)
> > clk |= MCI_FCEN; /* Bug fix in ST IP block */
> > This enables HW flow control on the block, and holds back
> > reads/writes so it doesn't over/underruns.
> Pierre used to argue that stopping the clock to the card was a bad
> thing, which is probably based on his experience dealing with SD/SDIO
> cards - so really the overrun/underrun problem is not a bug with the
Yep this is achieved by gating the clocks to the card indeed.
It will gate all clocks to the card, not just one, so MCIFBCLK
(i.e. the feedback clock from the card), MCICLKOUT (output to
the feedback loop) and MCICLK (main card clock) are all gated.
This has been in widespread use on the U300 platform under another
OS however, and no big problems have been reported. I believe this
is because we only have this platform fitted with uSD-cards in
practice, and those are late to the MMC/SD-show and may thus be
tolerant to this behaviour, something that may not apply to the
MMC cards of old times.
Another place where we use PL180 is with eMMC:s and here we
know the exact card in use, and we know that it will tolerate
So for us this frequency and HW gating seems to be acceptable
in practice though in theory we could solder in an MMC card holder
to the PL180.
More information about the linux-arm-kernel