From: H Hartley Sweeten <hartleys@visionengravers.com>
To: linux-mmc@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
cjb@laptop.org, hsweeten@visionengravers.com
Subject: Q: mmc au size
Date: Fri, 28 Jun 2013 16:46:21 -0700 [thread overview]
Message-ID: <201306281646.21319.hartleys@visionengravers.com> (raw)
Hello all,
I have a question concerning the "au" size of a SD Card.
I have an old Kingston 64MB SD-Card and lately I have noticed this
kernel message when I use the card:
mmc0: SD Status: Invalid Allocation Unit size.
This is due to the following commit:
commit b63b5e819d5b21ae493c17c356018ffa98d3ee1c
Author: Alan Cox <alan@linux.intel.com>
Date: Mon Jul 2 18:55:13 2012 +0100
mmc: core: correct invalid error checking
From the "SD Specifications, Part 1, Physical Layer Specification",
* AU_SIZE
This 4-bit field indicates AU Size and the value can be selected from
16 KB.
AU_SIZE Value Definition
------- ----------------
0h Not Defined
1h 16 KB
2h 32 KB
3h 64 KB
4h 128 KB
5h 256 KB
6h 512 KB
7h 1 MB
8h 2 MB
9h 4 MB
Ah 8 MB
Bh 12 MB
Ch 16 MB
Dh 24 MB
Eh 32 MB
Fh 64 MB
Also in the specification is this note:
Sector: is the unit that is related to the erase commands. Its size
is the number of blocks that will be erased in one portion. The size
of a sector is fixed for each device. The information about the sector
size (in blocks) is stored in the CSD. Note that if the card specifies
AU size, sector size should be ignored.
And this:
* SECTOR_SIZE
This field is fixed to 7Fh, which indicates 64 KBytes. This value does
not relate to erase operations. High Capacity and Extended Capacity
cards indicate memory boundary by AU size and this field should not
be used.
So, if an au size of 0 is reported wouldn't the erase size be the
sector size? If nothing else I think the test needs to be adjusted to
not report the error for an au size of 0.
Regards,
Hartley
reply other threads:[~2013-06-28 23:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201306281646.21319.hartleys@visionengravers.com \
--to=hartleys@visionengravers.com \
--cc=cjb@laptop.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.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