public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux-mmc@vger.kernel.org
Cc: arnd.bergmann@linaro.org, linux@horizon.com
Subject: SD 3.00 Physical layer FULL specification
Date: 31 Aug 2012 22:27:55 -0400	[thread overview]
Message-ID: <20120901022755.10343.qmail@science.horizon.com> (raw)

I was just trolling around the net trying to figure out what the
Pm parameter and speed class of SD cards meant, and I came across a
definitive answer in the form of a copy of Part 1 of the unredacted
v3.00 specification (April 16, 2009) at

http://www.61ic.com/code/attachment.php?aid=73871&k=cfaccbbb80c338769bd7282636c0ca7e&t=1331742726

I have of course snarfed a copy, and if anyone else on the list
would benefit from one, I figured it was worth sharing.

In particular, it documents the FAT update optimizations in SD cards
(section 4.3.1.7, p. 112).

If anyone cares, write performance is defined in terms of updates to
"allocation units" (i.e. erase blocks) 512K-4MiB in size of a card-defined
size, which are made up of "recording units" (i.e. FAT clusters).
Table 4-51 on p. 113 gives the limits.

An update to an allocation unit is a combination of writes of new data
and and moves (copies) of old data from the pre-existing AU.  Each of
these has a performance standard, Pw and Pm, respectively.

For a "Class n" card, Pw and Pr must be >= n MB/s, while Pm must be
>= n/2 MB/s.  (Exacpt, oddly, class 10 has NO lower bound on Pm.)

             reply	other threads:[~2012-09-01  2:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-01  2:27 George Spelvin [this message]
2012-09-01 20:19 ` SD 3.00 Physical layer FULL specification Arnd Bergmann

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=20120901022755.10343.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=linux-mmc@vger.kernel.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