2006-12-30 16:11:32 -07:00
|
|
|
/*
|
2007-07-11 11:04:50 -07:00
|
|
|
* linux/drivers/mmc/core/sd.c
|
2006-12-30 16:11:32 -07:00
|
|
|
*
|
|
|
|
* Copyright (C) 2003-2004 Russell King, All Rights Reserved.
|
|
|
|
* SD support Copyright (C) 2004 Ian Molton, All Rights Reserved.
|
|
|
|
* Copyright (C) 2005-2007 Pierre Ossman, All Rights Reserved.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/err.h>
|
2013-11-25 18:16:25 -07:00
|
|
|
#include <linux/sizes.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 01:04:11 -07:00
|
|
|
#include <linux/slab.h>
|
2011-07-15 09:01:27 -07:00
|
|
|
#include <linux/stat.h>
|
2013-10-10 05:20:05 -07:00
|
|
|
#include <linux/pm_runtime.h>
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
#include <linux/mmc/host.h>
|
|
|
|
#include <linux/mmc/card.h>
|
|
|
|
#include <linux/mmc/mmc.h>
|
2007-05-31 13:25:11 -07:00
|
|
|
#include <linux/mmc/sd.h>
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
#include "core.h"
|
2017-01-13 06:14:14 -07:00
|
|
|
#include "card.h"
|
2017-01-13 06:14:15 -07:00
|
|
|
#include "host.h"
|
2007-05-19 04:39:01 -07:00
|
|
|
#include "bus.h"
|
2006-12-30 16:11:32 -07:00
|
|
|
#include "mmc_ops.h"
|
2011-02-10 03:58:37 -07:00
|
|
|
#include "sd.h"
|
2006-12-30 16:11:32 -07:00
|
|
|
#include "sd_ops.h"
|
|
|
|
|
|
|
|
static const unsigned int tran_exp[] = {
|
|
|
|
10000, 100000, 1000000, 10000000,
|
|
|
|
0, 0, 0, 0
|
|
|
|
};
|
|
|
|
|
|
|
|
static const unsigned char tran_mant[] = {
|
|
|
|
0, 10, 12, 13, 15, 20, 25, 30,
|
|
|
|
35, 40, 45, 50, 55, 60, 70, 80,
|
|
|
|
};
|
|
|
|
|
2017-08-01 20:12:42 -07:00
|
|
|
static const unsigned int taac_exp[] = {
|
2006-12-30 16:11:32 -07:00
|
|
|
1, 10, 100, 1000, 10000, 100000, 1000000, 10000000,
|
|
|
|
};
|
|
|
|
|
2017-08-01 20:12:42 -07:00
|
|
|
static const unsigned int taac_mant[] = {
|
2006-12-30 16:11:32 -07:00
|
|
|
0, 10, 12, 13, 15, 20, 25, 30,
|
|
|
|
35, 40, 45, 50, 55, 60, 70, 80,
|
|
|
|
};
|
|
|
|
|
2013-11-25 18:16:25 -07:00
|
|
|
static const unsigned int sd_au_size[] = {
|
|
|
|
0, SZ_16K / 512, SZ_32K / 512, SZ_64K / 512,
|
|
|
|
SZ_128K / 512, SZ_256K / 512, SZ_512K / 512, SZ_1M / 512,
|
|
|
|
SZ_2M / 512, SZ_4M / 512, SZ_8M / 512, (SZ_8M + SZ_4M) / 512,
|
|
|
|
SZ_16M / 512, (SZ_16M + SZ_8M) / 512, SZ_32M / 512, SZ_64M / 512,
|
|
|
|
};
|
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
#define UNSTUFF_BITS(resp,start,size) \
|
|
|
|
({ \
|
|
|
|
const int __size = size; \
|
|
|
|
const u32 __mask = (__size < 32 ? 1 << __size : 0) - 1; \
|
|
|
|
const int __off = 3 - ((start) / 32); \
|
|
|
|
const int __shft = (start) & 31; \
|
|
|
|
u32 __res; \
|
|
|
|
\
|
|
|
|
__res = resp[__off] >> __shft; \
|
|
|
|
if (__size + __shft > 32) \
|
|
|
|
__res |= resp[__off-1] << ((32 - __shft) % 32); \
|
|
|
|
__res & __mask; \
|
|
|
|
})
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Given the decoded CSD structure, decode the raw CID to our CID structure.
|
|
|
|
*/
|
2010-08-10 18:01:40 -07:00
|
|
|
void mmc_decode_cid(struct mmc_card *card)
|
2006-12-30 16:11:32 -07:00
|
|
|
{
|
|
|
|
u32 *resp = card->raw_cid;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* SD doesn't currently have a version field so we will
|
|
|
|
* have to assume we can parse this.
|
|
|
|
*/
|
|
|
|
card->cid.manfid = UNSTUFF_BITS(resp, 120, 8);
|
|
|
|
card->cid.oemid = UNSTUFF_BITS(resp, 104, 16);
|
|
|
|
card->cid.prod_name[0] = UNSTUFF_BITS(resp, 96, 8);
|
|
|
|
card->cid.prod_name[1] = UNSTUFF_BITS(resp, 88, 8);
|
|
|
|
card->cid.prod_name[2] = UNSTUFF_BITS(resp, 80, 8);
|
|
|
|
card->cid.prod_name[3] = UNSTUFF_BITS(resp, 72, 8);
|
|
|
|
card->cid.prod_name[4] = UNSTUFF_BITS(resp, 64, 8);
|
|
|
|
card->cid.hwrev = UNSTUFF_BITS(resp, 60, 4);
|
|
|
|
card->cid.fwrev = UNSTUFF_BITS(resp, 56, 4);
|
|
|
|
card->cid.serial = UNSTUFF_BITS(resp, 24, 32);
|
|
|
|
card->cid.year = UNSTUFF_BITS(resp, 12, 8);
|
|
|
|
card->cid.month = UNSTUFF_BITS(resp, 8, 4);
|
|
|
|
|
|
|
|
card->cid.year += 2000; /* SD cards year offset */
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Given a 128-bit response, decode to our card CSD structure.
|
|
|
|
*/
|
2007-05-01 07:11:57 -07:00
|
|
|
static int mmc_decode_csd(struct mmc_card *card)
|
2006-12-30 16:11:32 -07:00
|
|
|
{
|
|
|
|
struct mmc_csd *csd = &card->csd;
|
|
|
|
unsigned int e, m, csd_struct;
|
|
|
|
u32 *resp = card->raw_csd;
|
|
|
|
|
|
|
|
csd_struct = UNSTUFF_BITS(resp, 126, 2);
|
|
|
|
|
|
|
|
switch (csd_struct) {
|
|
|
|
case 0:
|
|
|
|
m = UNSTUFF_BITS(resp, 115, 4);
|
|
|
|
e = UNSTUFF_BITS(resp, 112, 3);
|
2017-08-01 20:12:42 -07:00
|
|
|
csd->taac_ns = (taac_exp[e] * taac_mant[m] + 9) / 10;
|
|
|
|
csd->taac_clks = UNSTUFF_BITS(resp, 104, 8) * 100;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
m = UNSTUFF_BITS(resp, 99, 4);
|
|
|
|
e = UNSTUFF_BITS(resp, 96, 3);
|
|
|
|
csd->max_dtr = tran_exp[e] * tran_mant[m];
|
|
|
|
csd->cmdclass = UNSTUFF_BITS(resp, 84, 12);
|
|
|
|
|
|
|
|
e = UNSTUFF_BITS(resp, 47, 3);
|
|
|
|
m = UNSTUFF_BITS(resp, 62, 12);
|
|
|
|
csd->capacity = (1 + m) << (e + 2);
|
|
|
|
|
|
|
|
csd->read_blkbits = UNSTUFF_BITS(resp, 80, 4);
|
|
|
|
csd->read_partial = UNSTUFF_BITS(resp, 79, 1);
|
|
|
|
csd->write_misalign = UNSTUFF_BITS(resp, 78, 1);
|
|
|
|
csd->read_misalign = UNSTUFF_BITS(resp, 77, 1);
|
2014-08-19 01:45:51 -07:00
|
|
|
csd->dsr_imp = UNSTUFF_BITS(resp, 76, 1);
|
2006-12-30 16:11:32 -07:00
|
|
|
csd->r2w_factor = UNSTUFF_BITS(resp, 26, 3);
|
|
|
|
csd->write_blkbits = UNSTUFF_BITS(resp, 22, 4);
|
|
|
|
csd->write_partial = UNSTUFF_BITS(resp, 21, 1);
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
|
|
|
|
if (UNSTUFF_BITS(resp, 46, 1)) {
|
|
|
|
csd->erase_size = 1;
|
|
|
|
} else if (csd->write_blkbits >= 9) {
|
|
|
|
csd->erase_size = UNSTUFF_BITS(resp, 39, 7) + 1;
|
|
|
|
csd->erase_size <<= csd->write_blkbits - 9;
|
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
break;
|
|
|
|
case 1:
|
|
|
|
/*
|
2011-05-04 23:49:03 -07:00
|
|
|
* This is a block-addressed SDHC or SDXC card. Most
|
2006-12-30 16:11:32 -07:00
|
|
|
* interesting fields are unused and have fixed
|
|
|
|
* values. To avoid getting tripped by buggy cards,
|
|
|
|
* we assume those fixed values ourselves.
|
|
|
|
*/
|
|
|
|
mmc_card_set_blockaddr(card);
|
|
|
|
|
2017-08-01 20:12:42 -07:00
|
|
|
csd->taac_ns = 0; /* Unused */
|
|
|
|
csd->taac_clks = 0; /* Unused */
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
m = UNSTUFF_BITS(resp, 99, 4);
|
|
|
|
e = UNSTUFF_BITS(resp, 96, 3);
|
|
|
|
csd->max_dtr = tran_exp[e] * tran_mant[m];
|
|
|
|
csd->cmdclass = UNSTUFF_BITS(resp, 84, 12);
|
2011-05-04 23:49:03 -07:00
|
|
|
csd->c_size = UNSTUFF_BITS(resp, 48, 22);
|
|
|
|
|
|
|
|
/* SDXC cards have a minimum C_SIZE of 0x00FFFF */
|
|
|
|
if (csd->c_size >= 0xFFFF)
|
|
|
|
mmc_card_set_ext_capacity(card);
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
m = UNSTUFF_BITS(resp, 48, 22);
|
|
|
|
csd->capacity = (1 + m) << 10;
|
|
|
|
|
|
|
|
csd->read_blkbits = 9;
|
|
|
|
csd->read_partial = 0;
|
|
|
|
csd->write_misalign = 0;
|
|
|
|
csd->read_misalign = 0;
|
|
|
|
csd->r2w_factor = 4; /* Unused */
|
|
|
|
csd->write_blkbits = 9;
|
|
|
|
csd->write_partial = 0;
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
csd->erase_size = 1;
|
2006-12-30 16:11:32 -07:00
|
|
|
break;
|
|
|
|
default:
|
2011-10-10 23:14:09 -07:00
|
|
|
pr_err("%s: unrecognised CSD structure version %d\n",
|
2006-12-30 16:11:32 -07:00
|
|
|
mmc_hostname(card->host), csd_struct);
|
2007-05-01 07:11:57 -07:00
|
|
|
return -EINVAL;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
2007-05-01 07:11:57 -07:00
|
|
|
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
card->erase_size = csd->erase_size;
|
|
|
|
|
2007-05-01 07:11:57 -07:00
|
|
|
return 0;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Given a 64-bit response, decode to our card SCR structure.
|
|
|
|
*/
|
2007-05-01 07:11:57 -07:00
|
|
|
static int mmc_decode_scr(struct mmc_card *card)
|
2006-12-30 16:11:32 -07:00
|
|
|
{
|
|
|
|
struct sd_scr *scr = &card->scr;
|
|
|
|
unsigned int scr_struct;
|
|
|
|
u32 resp[4];
|
|
|
|
|
|
|
|
resp[3] = card->raw_scr[1];
|
|
|
|
resp[2] = card->raw_scr[0];
|
|
|
|
|
|
|
|
scr_struct = UNSTUFF_BITS(resp, 60, 4);
|
|
|
|
if (scr_struct != 0) {
|
2011-10-10 23:14:09 -07:00
|
|
|
pr_err("%s: unrecognised SCR structure version %d\n",
|
2006-12-30 16:11:32 -07:00
|
|
|
mmc_hostname(card->host), scr_struct);
|
2007-05-01 07:11:57 -07:00
|
|
|
return -EINVAL;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
scr->sda_vsn = UNSTUFF_BITS(resp, 56, 4);
|
|
|
|
scr->bus_widths = UNSTUFF_BITS(resp, 48, 4);
|
2011-05-04 23:48:58 -07:00
|
|
|
if (scr->sda_vsn == SCR_SPEC_VER_2)
|
|
|
|
/* Check if Physical Layer Spec v3.0 is supported */
|
|
|
|
scr->sda_spec3 = UNSTUFF_BITS(resp, 47, 1);
|
2007-05-01 07:11:57 -07:00
|
|
|
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
if (UNSTUFF_BITS(resp, 55, 1))
|
|
|
|
card->erased_byte = 0xFF;
|
|
|
|
else
|
|
|
|
card->erased_byte = 0x0;
|
|
|
|
|
2011-05-23 13:06:38 -07:00
|
|
|
if (scr->sda_spec3)
|
|
|
|
scr->cmds = UNSTUFF_BITS(resp, 32, 2);
|
2007-05-01 07:11:57 -07:00
|
|
|
return 0;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
|
|
|
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
/*
|
|
|
|
* Fetch and process SD Status register.
|
|
|
|
*/
|
|
|
|
static int mmc_read_ssr(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
unsigned int au, es, et, eo;
|
2017-04-02 13:56:03 -07:00
|
|
|
__be32 *raw_ssr;
|
2016-08-14 01:46:36 -07:00
|
|
|
int i;
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
|
|
|
|
if (!(card->csd.cmdclass & CCC_APP_SPEC)) {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: card lacks mandatory SD Status function\n",
|
|
|
|
mmc_hostname(card->host));
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-11-11 07:22:36 -07:00
|
|
|
raw_ssr = kmalloc(sizeof(card->raw_ssr), GFP_KERNEL);
|
|
|
|
if (!raw_ssr)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
if (mmc_app_sd_status(card, raw_ssr)) {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: problem reading SD Status register\n",
|
|
|
|
mmc_hostname(card->host));
|
2016-11-11 07:22:36 -07:00
|
|
|
kfree(raw_ssr);
|
2016-08-14 01:46:36 -07:00
|
|
|
return 0;
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < 16; i++)
|
2016-11-11 07:22:36 -07:00
|
|
|
card->raw_ssr[i] = be32_to_cpu(raw_ssr[i]);
|
|
|
|
|
|
|
|
kfree(raw_ssr);
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* UNSTUFF_BITS only works with four u32s so we have to offset the
|
|
|
|
* bitfield positions accordingly.
|
|
|
|
*/
|
2016-08-14 01:46:36 -07:00
|
|
|
au = UNSTUFF_BITS(card->raw_ssr, 428 - 384, 4);
|
2013-11-25 18:16:25 -07:00
|
|
|
if (au) {
|
|
|
|
if (au <= 9 || card->scr.sda_spec3) {
|
|
|
|
card->ssr.au = sd_au_size[au];
|
2016-08-14 01:46:36 -07:00
|
|
|
es = UNSTUFF_BITS(card->raw_ssr, 408 - 384, 16);
|
|
|
|
et = UNSTUFF_BITS(card->raw_ssr, 402 - 384, 6);
|
2013-11-25 18:16:25 -07:00
|
|
|
if (es && et) {
|
2016-08-14 01:46:36 -07:00
|
|
|
eo = UNSTUFF_BITS(card->raw_ssr, 400 - 384, 2);
|
2013-11-25 18:16:25 -07:00
|
|
|
card->ssr.erase_timeout = (et * 1000) / es;
|
|
|
|
card->ssr.erase_offset = eo * 1000;
|
|
|
|
}
|
|
|
|
} else {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: SD Status: Invalid Allocation Unit size\n",
|
|
|
|
mmc_hostname(card->host));
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
}
|
|
|
|
}
|
2016-08-14 01:46:36 -07:00
|
|
|
|
|
|
|
return 0;
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
}
|
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
/*
|
2007-05-01 05:46:08 -07:00
|
|
|
* Fetches and decodes switch information
|
2006-12-30 16:11:32 -07:00
|
|
|
*/
|
2007-05-01 05:46:08 -07:00
|
|
|
static int mmc_read_switch(struct mmc_card *card)
|
2006-12-30 16:11:32 -07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
u8 *status;
|
|
|
|
|
2007-05-31 13:25:11 -07:00
|
|
|
if (card->scr.sda_vsn < SCR_SPEC_VER_1)
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-31 13:25:11 -07:00
|
|
|
|
|
|
|
if (!(card->csd.cmdclass & CCC_SWITCH)) {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: card lacks mandatory switch function, performance might suffer\n",
|
2007-05-31 13:25:11 -07:00
|
|
|
mmc_hostname(card->host));
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-31 13:25:11 -07:00
|
|
|
}
|
|
|
|
|
2007-07-22 13:18:46 -07:00
|
|
|
err = -EIO;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
status = kmalloc(64, GFP_KERNEL);
|
2017-05-19 04:15:27 -07:00
|
|
|
if (!status)
|
2007-07-22 13:18:46 -07:00
|
|
|
return -ENOMEM;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2012-07-02 23:16:11 -07:00
|
|
|
/*
|
|
|
|
* Find out the card's support bits with a mode 0 operation.
|
|
|
|
* The argument does not matter, as the support bits do not
|
|
|
|
* change with the arguments.
|
|
|
|
*/
|
|
|
|
err = mmc_sd_switch(card, 0, 0, 0, status);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err) {
|
2011-05-04 23:48:58 -07:00
|
|
|
/*
|
|
|
|
* If the host or the card can't do the switch,
|
|
|
|
* fail more gracefully.
|
|
|
|
*/
|
|
|
|
if (err != -EINVAL && err != -ENOSYS && err != -EFAULT)
|
2007-07-22 14:08:30 -07:00
|
|
|
goto out;
|
|
|
|
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: problem reading Bus Speed modes\n",
|
2007-05-31 13:25:11 -07:00
|
|
|
mmc_hostname(card->host));
|
2007-07-22 13:18:46 -07:00
|
|
|
err = 0;
|
2007-07-22 14:08:30 -07:00
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2011-11-08 06:43:08 -07:00
|
|
|
if (status[13] & SD_MODE_HIGH_SPEED)
|
|
|
|
card->sw_caps.hs_max_dtr = HIGH_SPEED_MAX_DTR;
|
2011-08-09 22:46:01 -07:00
|
|
|
|
2011-05-04 23:48:58 -07:00
|
|
|
if (card->scr.sda_spec3) {
|
|
|
|
card->sw_caps.sd3_bus_mode = status[13];
|
2012-07-02 23:16:11 -07:00
|
|
|
/* Driver Strengths supported by the card */
|
2011-05-04 23:48:58 -07:00
|
|
|
card->sw_caps.sd3_drv_type = status[9];
|
2016-01-02 03:06:29 -07:00
|
|
|
card->sw_caps.sd3_curr_limit = status[7] | status[6] << 8;
|
2011-05-04 23:48:58 -07:00
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2007-05-01 05:46:08 -07:00
|
|
|
out:
|
|
|
|
kfree(status);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Test if the card supports high-speed mode and, if so, switch to it.
|
|
|
|
*/
|
2010-08-10 18:01:40 -07:00
|
|
|
int mmc_sd_switch_hs(struct mmc_card *card)
|
2007-05-01 05:46:08 -07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
u8 *status;
|
|
|
|
|
2007-05-31 13:25:11 -07:00
|
|
|
if (card->scr.sda_vsn < SCR_SPEC_VER_1)
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-31 13:25:11 -07:00
|
|
|
|
|
|
|
if (!(card->csd.cmdclass & CCC_SWITCH))
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-31 13:25:11 -07:00
|
|
|
|
2007-05-01 05:46:08 -07:00
|
|
|
if (!(card->host->caps & MMC_CAP_SD_HIGHSPEED))
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-01 05:46:08 -07:00
|
|
|
|
|
|
|
if (card->sw_caps.hs_max_dtr == 0)
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-01 05:46:08 -07:00
|
|
|
|
|
|
|
status = kmalloc(64, GFP_KERNEL);
|
2017-05-19 04:15:27 -07:00
|
|
|
if (!status)
|
2007-07-22 13:18:46 -07:00
|
|
|
return -ENOMEM;
|
2007-05-01 05:46:08 -07:00
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
err = mmc_sd_switch(card, 1, 0, 1, status);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2006-12-30 16:11:32 -07:00
|
|
|
goto out;
|
|
|
|
|
|
|
|
if ((status[16] & 0xF) != 1) {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: Problem switching card into high-speed mode!\n",
|
2006-12-30 16:11:32 -07:00
|
|
|
mmc_hostname(card->host));
|
2010-08-10 18:01:40 -07:00
|
|
|
err = 0;
|
2006-12-30 16:11:32 -07:00
|
|
|
} else {
|
2010-08-10 18:01:40 -07:00
|
|
|
err = 1;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
out:
|
|
|
|
kfree(status);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
static int sd_select_driver_type(struct mmc_card *card, u8 *status)
|
|
|
|
{
|
2015-02-06 05:12:53 -07:00
|
|
|
int card_drv_type, drive_strength, drv_type;
|
2011-05-04 23:48:59 -07:00
|
|
|
int err;
|
|
|
|
|
2015-02-06 05:12:56 -07:00
|
|
|
card->drive_strength = 0;
|
|
|
|
|
2015-02-06 05:12:53 -07:00
|
|
|
card_drv_type = card->sw_caps.sd3_drv_type | SD_DRIVER_TYPE_B;
|
2011-07-06 08:51:32 -07:00
|
|
|
|
2015-02-06 05:12:55 -07:00
|
|
|
drive_strength = mmc_select_drive_strength(card,
|
|
|
|
card->sw_caps.uhs_max_dtr,
|
|
|
|
card_drv_type, &drv_type);
|
2011-05-04 23:48:59 -07:00
|
|
|
|
2015-02-06 05:12:52 -07:00
|
|
|
if (drive_strength) {
|
|
|
|
err = mmc_sd_switch(card, 1, 2, drive_strength, status);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
if ((status[15] & 0xF) != drive_strength) {
|
|
|
|
pr_warn("%s: Problem setting drive strength!\n",
|
|
|
|
mmc_hostname(card->host));
|
|
|
|
return 0;
|
|
|
|
}
|
2015-02-06 05:12:56 -07:00
|
|
|
card->drive_strength = drive_strength;
|
2011-05-04 23:48:59 -07:00
|
|
|
}
|
|
|
|
|
2015-02-06 05:12:52 -07:00
|
|
|
if (drv_type)
|
|
|
|
mmc_set_driver_type(card->host, drv_type);
|
2011-05-04 23:48:59 -07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
static void sd_update_bus_speed_mode(struct mmc_card *card)
|
2011-05-04 23:49:01 -07:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* If the host doesn't support any of the UHS-I modes, fallback on
|
|
|
|
* default speed.
|
|
|
|
*/
|
2013-01-28 07:08:24 -07:00
|
|
|
if (!mmc_host_uhs(card->host)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = 0;
|
|
|
|
return;
|
|
|
|
}
|
2011-05-04 23:49:01 -07:00
|
|
|
|
|
|
|
if ((card->host->caps & MMC_CAP_UHS_SDR104) &&
|
|
|
|
(card->sw_caps.sd3_bus_mode & SD_MODE_UHS_SDR104)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = UHS_SDR104_BUS_SPEED;
|
2011-05-04 23:49:01 -07:00
|
|
|
} else if ((card->host->caps & MMC_CAP_UHS_DDR50) &&
|
|
|
|
(card->sw_caps.sd3_bus_mode & SD_MODE_UHS_DDR50)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = UHS_DDR50_BUS_SPEED;
|
2011-05-04 23:49:01 -07:00
|
|
|
} else if ((card->host->caps & (MMC_CAP_UHS_SDR104 |
|
|
|
|
MMC_CAP_UHS_SDR50)) && (card->sw_caps.sd3_bus_mode &
|
|
|
|
SD_MODE_UHS_SDR50)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = UHS_SDR50_BUS_SPEED;
|
2011-05-04 23:49:01 -07:00
|
|
|
} else if ((card->host->caps & (MMC_CAP_UHS_SDR104 |
|
|
|
|
MMC_CAP_UHS_SDR50 | MMC_CAP_UHS_SDR25)) &&
|
|
|
|
(card->sw_caps.sd3_bus_mode & SD_MODE_UHS_SDR25)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = UHS_SDR25_BUS_SPEED;
|
2011-05-04 23:49:01 -07:00
|
|
|
} else if ((card->host->caps & (MMC_CAP_UHS_SDR104 |
|
|
|
|
MMC_CAP_UHS_SDR50 | MMC_CAP_UHS_SDR25 |
|
|
|
|
MMC_CAP_UHS_SDR12)) && (card->sw_caps.sd3_bus_mode &
|
|
|
|
SD_MODE_UHS_SDR12)) {
|
2011-08-08 23:49:31 -07:00
|
|
|
card->sd_bus_speed = UHS_SDR12_BUS_SPEED;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static int sd_set_bus_speed_mode(struct mmc_card *card, u8 *status)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
unsigned int timing = 0;
|
|
|
|
|
|
|
|
switch (card->sd_bus_speed) {
|
|
|
|
case UHS_SDR104_BUS_SPEED:
|
|
|
|
timing = MMC_TIMING_UHS_SDR104;
|
|
|
|
card->sw_caps.uhs_max_dtr = UHS_SDR104_MAX_DTR;
|
|
|
|
break;
|
|
|
|
case UHS_DDR50_BUS_SPEED:
|
|
|
|
timing = MMC_TIMING_UHS_DDR50;
|
|
|
|
card->sw_caps.uhs_max_dtr = UHS_DDR50_MAX_DTR;
|
|
|
|
break;
|
|
|
|
case UHS_SDR50_BUS_SPEED:
|
|
|
|
timing = MMC_TIMING_UHS_SDR50;
|
|
|
|
card->sw_caps.uhs_max_dtr = UHS_SDR50_MAX_DTR;
|
|
|
|
break;
|
|
|
|
case UHS_SDR25_BUS_SPEED:
|
|
|
|
timing = MMC_TIMING_UHS_SDR25;
|
|
|
|
card->sw_caps.uhs_max_dtr = UHS_SDR25_MAX_DTR;
|
|
|
|
break;
|
|
|
|
case UHS_SDR12_BUS_SPEED:
|
|
|
|
timing = MMC_TIMING_UHS_SDR12;
|
|
|
|
card->sw_caps.uhs_max_dtr = UHS_SDR12_MAX_DTR;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return 0;
|
2011-05-04 23:49:01 -07:00
|
|
|
}
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
err = mmc_sd_switch(card, 1, 0, card->sd_bus_speed, status);
|
2011-05-04 23:49:01 -07:00
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
if ((status[16] & 0xF) != card->sd_bus_speed)
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: Problem setting bus speed mode!\n",
|
2011-05-04 23:49:01 -07:00
|
|
|
mmc_hostname(card->host));
|
|
|
|
else {
|
|
|
|
mmc_set_timing(card->host, timing);
|
|
|
|
mmc_set_clock(card->host, card->sw_caps.uhs_max_dtr);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-07-03 22:31:48 -07:00
|
|
|
/* Get host's max current setting at its current voltage */
|
|
|
|
static u32 sd_get_host_max_current(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
u32 voltage, max_current;
|
|
|
|
|
|
|
|
voltage = 1 << host->ios.vdd;
|
|
|
|
switch (voltage) {
|
|
|
|
case MMC_VDD_165_195:
|
|
|
|
max_current = host->max_current_180;
|
|
|
|
break;
|
|
|
|
case MMC_VDD_29_30:
|
|
|
|
case MMC_VDD_30_31:
|
|
|
|
max_current = host->max_current_300;
|
|
|
|
break;
|
|
|
|
case MMC_VDD_32_33:
|
|
|
|
case MMC_VDD_33_34:
|
|
|
|
max_current = host->max_current_330;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
max_current = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return max_current;
|
|
|
|
}
|
|
|
|
|
2011-05-04 23:49:02 -07:00
|
|
|
static int sd_set_current_limit(struct mmc_card *card, u8 *status)
|
|
|
|
{
|
2012-05-27 18:36:33 -07:00
|
|
|
int current_limit = SD_SET_CURRENT_NO_CHANGE;
|
2011-05-04 23:49:02 -07:00
|
|
|
int err;
|
2012-07-03 22:31:48 -07:00
|
|
|
u32 max_current;
|
2011-05-04 23:49:02 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Current limit switch is only defined for SDR50, SDR104, and DDR50
|
2012-05-27 18:36:33 -07:00
|
|
|
* bus speed modes. For other bus speed modes, we do not change the
|
|
|
|
* current limit.
|
2012-07-03 22:31:48 -07:00
|
|
|
*/
|
|
|
|
if ((card->sd_bus_speed != UHS_SDR50_BUS_SPEED) &&
|
|
|
|
(card->sd_bus_speed != UHS_SDR104_BUS_SPEED) &&
|
|
|
|
(card->sd_bus_speed != UHS_DDR50_BUS_SPEED))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Host has different current capabilities when operating at
|
|
|
|
* different voltages, so find out its max current first.
|
|
|
|
*/
|
|
|
|
max_current = sd_get_host_max_current(card->host);
|
|
|
|
|
|
|
|
/*
|
2012-07-02 23:16:11 -07:00
|
|
|
* We only check host's capability here, if we set a limit that is
|
|
|
|
* higher than the card's maximum current, the card will be using its
|
|
|
|
* maximum current, e.g. if the card's maximum current is 300ma, and
|
|
|
|
* when we set current limit to 200ma, the card will draw 200ma, and
|
|
|
|
* when we set current limit to 400/600/800ma, the card will draw its
|
|
|
|
* maximum 300ma from the host.
|
2016-01-02 03:06:29 -07:00
|
|
|
*
|
|
|
|
* The above is incorrect: if we try to set a current limit that is
|
|
|
|
* not supported by the card, the card can rightfully error out the
|
|
|
|
* attempt, and remain at the default current limit. This results
|
|
|
|
* in a 300mA card being limited to 200mA even though the host
|
|
|
|
* supports 800mA. Failures seen with SanDisk 8GB UHS cards with
|
|
|
|
* an iMX6 host. --rmk
|
2011-05-04 23:49:02 -07:00
|
|
|
*/
|
2016-01-02 03:06:29 -07:00
|
|
|
if (max_current >= 800 &&
|
|
|
|
card->sw_caps.sd3_curr_limit & SD_MAX_CURRENT_800)
|
2012-07-03 22:31:48 -07:00
|
|
|
current_limit = SD_SET_CURRENT_LIMIT_800;
|
2016-01-02 03:06:29 -07:00
|
|
|
else if (max_current >= 600 &&
|
|
|
|
card->sw_caps.sd3_curr_limit & SD_MAX_CURRENT_600)
|
2012-07-03 22:31:48 -07:00
|
|
|
current_limit = SD_SET_CURRENT_LIMIT_600;
|
2016-01-02 03:06:29 -07:00
|
|
|
else if (max_current >= 400 &&
|
|
|
|
card->sw_caps.sd3_curr_limit & SD_MAX_CURRENT_400)
|
2012-07-03 22:31:48 -07:00
|
|
|
current_limit = SD_SET_CURRENT_LIMIT_400;
|
2016-01-02 03:06:29 -07:00
|
|
|
else if (max_current >= 200 &&
|
|
|
|
card->sw_caps.sd3_curr_limit & SD_MAX_CURRENT_200)
|
2012-07-03 22:31:48 -07:00
|
|
|
current_limit = SD_SET_CURRENT_LIMIT_200;
|
2011-05-04 23:49:02 -07:00
|
|
|
|
2012-05-27 18:36:33 -07:00
|
|
|
if (current_limit != SD_SET_CURRENT_NO_CHANGE) {
|
|
|
|
err = mmc_sd_switch(card, 1, 3, current_limit, status);
|
|
|
|
if (err)
|
|
|
|
return err;
|
2011-05-04 23:49:02 -07:00
|
|
|
|
2012-05-27 18:36:33 -07:00
|
|
|
if (((status[15] >> 4) & 0x0F) != current_limit)
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: Problem setting current limit!\n",
|
2012-05-27 18:36:33 -07:00
|
|
|
mmc_hostname(card->host));
|
2011-05-04 23:49:02 -07:00
|
|
|
|
2012-05-27 18:36:33 -07:00
|
|
|
}
|
2012-07-02 23:16:11 -07:00
|
|
|
|
2011-05-04 23:49:02 -07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
/*
|
|
|
|
* UHS-I specific initialization procedure
|
|
|
|
*/
|
|
|
|
static int mmc_sd_init_uhs_card(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
u8 *status;
|
|
|
|
|
|
|
|
if (!card->scr.sda_spec3)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (!(card->csd.cmdclass & CCC_SWITCH))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
status = kmalloc(64, GFP_KERNEL);
|
2017-05-19 04:15:27 -07:00
|
|
|
if (!status)
|
2011-05-04 23:48:59 -07:00
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
/* Set 4-bit bus width */
|
|
|
|
if ((card->host->caps & MMC_CAP_4_BIT_DATA) &&
|
|
|
|
(card->scr.bus_widths & SD_SCR_BUS_WIDTH_4)) {
|
|
|
|
err = mmc_app_set_bus_width(card, MMC_BUS_WIDTH_4);
|
|
|
|
if (err)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
mmc_set_bus_width(card->host, MMC_BUS_WIDTH_4);
|
|
|
|
}
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
/*
|
|
|
|
* Select the bus speed mode depending on host
|
|
|
|
* and card capability.
|
|
|
|
*/
|
|
|
|
sd_update_bus_speed_mode(card);
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
/* Set the driver strength for the card */
|
|
|
|
err = sd_select_driver_type(card, status);
|
2011-05-04 23:49:01 -07:00
|
|
|
if (err)
|
|
|
|
goto out;
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
/* Set current limit for the card */
|
|
|
|
err = sd_set_current_limit(card, status);
|
2011-05-04 23:49:02 -07:00
|
|
|
if (err)
|
|
|
|
goto out;
|
|
|
|
|
2011-08-08 23:49:31 -07:00
|
|
|
/* Set bus speed mode of the card */
|
|
|
|
err = sd_set_bus_speed_mode(card, status);
|
2011-05-04 23:49:04 -07:00
|
|
|
if (err)
|
|
|
|
goto out;
|
|
|
|
|
2013-04-17 04:50:53 -07:00
|
|
|
/*
|
|
|
|
* SPI mode doesn't define CMD19 and tuning is only valid for SDR50 and
|
|
|
|
* SDR104 mode SD-cards. Note that tuning is mandatory for SDR104.
|
|
|
|
*/
|
2014-12-05 10:40:59 -07:00
|
|
|
if (!mmc_host_is_spi(card->host) &&
|
2016-01-13 01:36:55 -07:00
|
|
|
(card->host->ios.timing == MMC_TIMING_UHS_SDR50 ||
|
|
|
|
card->host->ios.timing == MMC_TIMING_UHS_DDR50 ||
|
|
|
|
card->host->ios.timing == MMC_TIMING_UHS_SDR104)) {
|
2014-12-05 10:40:59 -07:00
|
|
|
err = mmc_execute_tuning(card);
|
2015-10-04 05:04:11 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* As SD Specifications Part1 Physical Layer Specification
|
|
|
|
* Version 3.01 says, CMD19 tuning is available for unlocked
|
|
|
|
* cards in transfer state of 1.8V signaling mode. The small
|
|
|
|
* difference between v3.00 and 3.01 spec means that CMD19
|
|
|
|
* tuning is also available for DDR50 mode.
|
|
|
|
*/
|
2016-01-13 01:36:55 -07:00
|
|
|
if (err && card->host->ios.timing == MMC_TIMING_UHS_DDR50) {
|
2015-10-04 05:04:11 -07:00
|
|
|
pr_warn("%s: ddr50 tuning failed\n",
|
|
|
|
mmc_hostname(card->host));
|
|
|
|
err = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
out:
|
|
|
|
kfree(status);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2008-03-21 15:54:50 -07:00
|
|
|
MMC_DEV_ATTR(cid, "%08x%08x%08x%08x\n", card->raw_cid[0], card->raw_cid[1],
|
|
|
|
card->raw_cid[2], card->raw_cid[3]);
|
|
|
|
MMC_DEV_ATTR(csd, "%08x%08x%08x%08x\n", card->raw_csd[0], card->raw_csd[1],
|
|
|
|
card->raw_csd[2], card->raw_csd[3]);
|
|
|
|
MMC_DEV_ATTR(scr, "%08x%08x\n", card->raw_scr[0], card->raw_scr[1]);
|
2016-08-14 01:46:36 -07:00
|
|
|
MMC_DEV_ATTR(ssr,
|
|
|
|
"%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x%08x\n",
|
|
|
|
card->raw_ssr[0], card->raw_ssr[1], card->raw_ssr[2],
|
|
|
|
card->raw_ssr[3], card->raw_ssr[4], card->raw_ssr[5],
|
|
|
|
card->raw_ssr[6], card->raw_ssr[7], card->raw_ssr[8],
|
|
|
|
card->raw_ssr[9], card->raw_ssr[10], card->raw_ssr[11],
|
|
|
|
card->raw_ssr[12], card->raw_ssr[13], card->raw_ssr[14],
|
|
|
|
card->raw_ssr[15]);
|
2008-03-21 15:54:50 -07:00
|
|
|
MMC_DEV_ATTR(date, "%02d/%04d\n", card->cid.month, card->cid.year);
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
MMC_DEV_ATTR(erase_size, "%u\n", card->erase_size << 9);
|
|
|
|
MMC_DEV_ATTR(preferred_erase_size, "%u\n", card->pref_erase << 9);
|
2008-03-21 15:54:50 -07:00
|
|
|
MMC_DEV_ATTR(fwrev, "0x%x\n", card->cid.fwrev);
|
|
|
|
MMC_DEV_ATTR(hwrev, "0x%x\n", card->cid.hwrev);
|
|
|
|
MMC_DEV_ATTR(manfid, "0x%06x\n", card->cid.manfid);
|
|
|
|
MMC_DEV_ATTR(name, "%s\n", card->cid.prod_name);
|
|
|
|
MMC_DEV_ATTR(oemid, "0x%04x\n", card->cid.oemid);
|
|
|
|
MMC_DEV_ATTR(serial, "0x%08x\n", card->cid.serial);
|
2016-07-04 04:56:55 -07:00
|
|
|
MMC_DEV_ATTR(ocr, "%08x\n", card->ocr);
|
2008-03-21 15:54:50 -07:00
|
|
|
|
|
|
|
|
2016-07-19 02:16:38 -07:00
|
|
|
static ssize_t mmc_dsr_show(struct device *dev,
|
|
|
|
struct device_attribute *attr,
|
|
|
|
char *buf)
|
|
|
|
{
|
|
|
|
struct mmc_card *card = mmc_dev_to_card(dev);
|
|
|
|
struct mmc_host *host = card->host;
|
|
|
|
|
|
|
|
if (card->csd.dsr_imp && host->dsr_req)
|
|
|
|
return sprintf(buf, "0x%x\n", host->dsr);
|
|
|
|
else
|
|
|
|
/* return default DSR value */
|
|
|
|
return sprintf(buf, "0x%x\n", 0x404);
|
|
|
|
}
|
|
|
|
|
|
|
|
static DEVICE_ATTR(dsr, S_IRUGO, mmc_dsr_show, NULL);
|
|
|
|
|
2008-03-21 15:54:50 -07:00
|
|
|
static struct attribute *sd_std_attrs[] = {
|
|
|
|
&dev_attr_cid.attr,
|
|
|
|
&dev_attr_csd.attr,
|
|
|
|
&dev_attr_scr.attr,
|
2016-08-14 01:46:36 -07:00
|
|
|
&dev_attr_ssr.attr,
|
2008-03-21 15:54:50 -07:00
|
|
|
&dev_attr_date.attr,
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
&dev_attr_erase_size.attr,
|
|
|
|
&dev_attr_preferred_erase_size.attr,
|
2008-03-21 15:54:50 -07:00
|
|
|
&dev_attr_fwrev.attr,
|
|
|
|
&dev_attr_hwrev.attr,
|
|
|
|
&dev_attr_manfid.attr,
|
|
|
|
&dev_attr_name.attr,
|
|
|
|
&dev_attr_oemid.attr,
|
|
|
|
&dev_attr_serial.attr,
|
2016-07-04 04:56:55 -07:00
|
|
|
&dev_attr_ocr.attr,
|
2016-07-19 02:16:38 -07:00
|
|
|
&dev_attr_dsr.attr,
|
2008-03-21 15:54:50 -07:00
|
|
|
NULL,
|
|
|
|
};
|
2014-03-08 00:05:27 -07:00
|
|
|
ATTRIBUTE_GROUPS(sd_std);
|
2008-03-21 15:54:50 -07:00
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
struct device_type sd_type = {
|
2014-03-08 00:05:27 -07:00
|
|
|
.groups = sd_std_groups,
|
2008-03-21 15:54:50 -07:00
|
|
|
};
|
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
/*
|
2010-08-10 18:01:40 -07:00
|
|
|
* Fetch CID from card.
|
2006-12-30 16:11:32 -07:00
|
|
|
*/
|
2011-05-04 23:48:59 -07:00
|
|
|
int mmc_sd_get_cid(struct mmc_host *host, u32 ocr, u32 *cid, u32 *rocr)
|
2006-12-30 16:11:32 -07:00
|
|
|
{
|
|
|
|
int err;
|
2012-07-03 22:31:48 -07:00
|
|
|
u32 max_current;
|
2013-01-28 07:08:28 -07:00
|
|
|
int retries = 10;
|
2013-09-13 02:31:33 -07:00
|
|
|
u32 pocr = ocr;
|
2013-01-28 07:08:28 -07:00
|
|
|
|
|
|
|
try_again:
|
|
|
|
if (!retries) {
|
|
|
|
ocr &= ~SD_OCR_S18R;
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: Skipping voltage switch\n", mmc_hostname(host));
|
2013-01-28 07:08:28 -07:00
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Since we're changing the OCR value, we seem to
|
|
|
|
* need to tell some cards to go back to the idle
|
|
|
|
* state. We wait 1ms to give cards time to
|
|
|
|
* respond.
|
|
|
|
*/
|
|
|
|
mmc_go_idle(host);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If SD_SEND_IF_COND indicates an SD 2.0
|
|
|
|
* compliant card and we should set bit 30
|
|
|
|
* of the ocr to indicate that we can handle
|
|
|
|
* block-addressed SDHC cards.
|
|
|
|
*/
|
2007-05-01 07:00:02 -07:00
|
|
|
err = mmc_send_if_cond(host, ocr);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (!err)
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
ocr |= SD_OCR_CCS;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
/*
|
|
|
|
* If the host supports one of UHS-I modes, request the card
|
2013-01-28 07:08:28 -07:00
|
|
|
* to switch to 1.8V signaling level. If the card has failed
|
|
|
|
* repeatedly to switch however, skip this.
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
*/
|
2013-01-28 07:08:28 -07:00
|
|
|
if (retries && mmc_host_uhs(host))
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
ocr |= SD_OCR_S18R;
|
|
|
|
|
2012-07-03 22:31:48 -07:00
|
|
|
/*
|
|
|
|
* If the host can supply more than 150mA at current voltage,
|
|
|
|
* XPC should be set to 1.
|
|
|
|
*/
|
|
|
|
max_current = sd_get_host_max_current(host);
|
|
|
|
if (max_current > 150)
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
ocr |= SD_OCR_XPC;
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
err = mmc_send_app_op_cond(host, ocr, rocr);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2010-08-10 18:01:40 -07:00
|
|
|
return err;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
/*
|
|
|
|
* In case CCS and S18A in the response is set, start Signal Voltage
|
|
|
|
* Switch procedure. SPI mode doesn't support CMD11.
|
|
|
|
*/
|
2011-05-04 23:48:59 -07:00
|
|
|
if (!mmc_host_is_spi(host) && rocr &&
|
|
|
|
((*rocr & 0x41000000) == 0x41000000)) {
|
2017-01-25 02:25:01 -07:00
|
|
|
err = mmc_set_uhs_voltage(host, pocr);
|
2013-01-28 07:08:28 -07:00
|
|
|
if (err == -EAGAIN) {
|
|
|
|
retries--;
|
|
|
|
goto try_again;
|
|
|
|
} else if (err) {
|
|
|
|
retries = 0;
|
mmc: sd: add support for signal voltage switch procedure
Host Controller v3.00 adds another Capabilities register. Apart
from other things, this new register indicates whether the Host
Controller supports SDR50, SDR104, and DDR50 UHS-I modes. The spec
doesn't mention about explicit support for SDR12 and SDR25 UHS-I
modes, so the Host Controller v3.00 should support them by default.
Also if the controller supports SDR104 mode, it will also support
SDR50 mode as well. So depending on the host support, we set the
corresponding MMC_CAP_* flags. One more new register. Host Control2
is added in v3.00, which is used during Signal Voltage Switch
procedure described below.
Since as per v3.00 spec, UHS-I supported hosts should set S18R
to 1, we set S18R (bit 24) of OCR before sending ACMD41. We also
need to set XPC (bit 28) of OCR in case the host can supply >150mA.
This support is indicated by the Maximum Current Capabilities
register of the Host Controller.
If the response of ACMD41 has both CCS and S18A set, we start the
signal voltage switch procedure, which if successfull, will switch
the card from 3.3V signalling to 1.8V signalling. Signal voltage
switch procedure adds support for a new command CMD11 in the
Physical Layer Spec v3.01. As part of this procedure, we need to
set 1.8V Signalling Enable (bit 3) of Host Control2 register, which
if remains set after 5ms, means the switch to 1.8V signalling is
successfull. Otherwise, we clear bit 24 of OCR and retry the
initialization sequence. When we remove the card, and insert the
same or another card, we need to make sure that we start with 3.3V
signalling voltage. So we call mmc_set_signal_voltage() with
MMC_SIGNAL_VOLTAGE_330 set so that we are back to 3.3V signalling
voltage before we actually start initializing the card.
Tested by Zhangfei Gao with a Toshiba uhs card and general hs card,
on mmp2 in SDMA mode.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Reviewed-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Acked-by: Zhangfei Gao <zhangfei.gao@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
2011-05-04 23:48:57 -07:00
|
|
|
goto try_again;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-06-08 06:27:43 -07:00
|
|
|
err = mmc_send_cid(host, cid);
|
2010-08-10 18:01:40 -07:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
int mmc_sd_get_csd(struct mmc_host *host, struct mmc_card *card)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Fetch CSD from card.
|
|
|
|
*/
|
|
|
|
err = mmc_send_csd(card, card->raw_csd);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2010-08-10 18:01:40 -07:00
|
|
|
return err;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
err = mmc_decode_csd(card);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2015-05-06 11:31:19 -07:00
|
|
|
static int mmc_sd_get_ro(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int ro;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Some systems don't feature a write-protect pin and don't need one.
|
|
|
|
* E.g. because they only have micro-SD card slot. For those systems
|
|
|
|
* assume that the SD card is always read-write.
|
|
|
|
*/
|
|
|
|
if (host->caps2 & MMC_CAP2_NO_WRITE_PROTECT)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (!host->ops->get_ro)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
ro = host->ops->get_ro(host);
|
|
|
|
|
|
|
|
return ro;
|
|
|
|
}
|
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
int mmc_sd_setup_card(struct mmc_host *host, struct mmc_card *card,
|
|
|
|
bool reinit)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (!reinit) {
|
|
|
|
/*
|
|
|
|
* Fetch SCR from card.
|
|
|
|
*/
|
2017-04-02 13:56:03 -07:00
|
|
|
err = mmc_app_send_scr(card);
|
2010-08-10 18:01:40 -07:00
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
err = mmc_decode_scr(card);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
mmc: add erase, secure erase, trim and secure trim operations
SD/MMC cards tend to support an erase operation. In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.
SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.
"erase_size" is the minimum size, in bytes, of an erase operation. For
MMC, "erase_size" is the erase group size reported by the card. Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector. For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.
SD/MMC cards can erase an arbitrarily large area up to and
including the whole card. When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:
1. A single erase command will make all other I/O on the card
wait. This is not a problem if the whole card is being erased, but
erasing one partition will make I/O for another partition on the
same card wait for the duration of the erase - which could be a
several minutes.
2. To be able to inform the user of erase progress.
3. The erase timeout becomes too large to be very useful.
Because the erase timeout contains a margin which is multiplied by
the size of the erase area, the value can end up being several
minutes for large areas.
"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.
For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.
For SD, "preferred_erase_size" is the allocation unit size specified by
the card.
"preferred_erase_size" is in bytes.
Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Acked-by: Jens Axboe <axboe@kernel.dk>
Cc: Kyungmin Park <kmpark@infradead.org>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-08-11 14:17:46 -07:00
|
|
|
/*
|
|
|
|
* Fetch and process SD Status register.
|
|
|
|
*/
|
|
|
|
err = mmc_read_ssr(card);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
/* Erase init depends on CSD and SSR */
|
|
|
|
mmc_init_erase(card);
|
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
/*
|
|
|
|
* Fetch switch information from card.
|
|
|
|
*/
|
|
|
|
err = mmc_read_switch(card);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* For SPI, enable CRC as appropriate.
|
|
|
|
* This CRC enable is located AFTER the reading of the
|
|
|
|
* card registers because some SDHC cards are not able
|
|
|
|
* to provide valid CRCs for non-512-byte blocks.
|
|
|
|
*/
|
|
|
|
if (mmc_host_is_spi(host)) {
|
|
|
|
err = mmc_spi_set_crc(host, use_spi_crc);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Check if read-only switch is active.
|
|
|
|
*/
|
|
|
|
if (!reinit) {
|
2015-05-06 11:31:19 -07:00
|
|
|
int ro = mmc_sd_get_ro(host);
|
2010-08-10 18:01:40 -07:00
|
|
|
|
|
|
|
if (ro < 0) {
|
2014-09-12 14:56:56 -07:00
|
|
|
pr_warn("%s: host does not support reading read-only switch, assuming write-enable\n",
|
2010-08-10 18:01:40 -07:00
|
|
|
mmc_hostname(host));
|
|
|
|
} else if (ro > 0) {
|
|
|
|
mmc_card_set_readonly(card);
|
2007-07-22 14:08:30 -07:00
|
|
|
}
|
2010-08-10 18:01:40 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
unsigned mmc_sd_get_max_clock(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
unsigned max_dtr = (unsigned int)-1;
|
|
|
|
|
2014-04-23 01:07:35 -07:00
|
|
|
if (mmc_card_hs(card)) {
|
2010-08-10 18:01:40 -07:00
|
|
|
if (max_dtr > card->sw_caps.hs_max_dtr)
|
|
|
|
max_dtr = card->sw_caps.hs_max_dtr;
|
|
|
|
} else if (max_dtr > card->csd.max_dtr) {
|
|
|
|
max_dtr = card->csd.max_dtr;
|
|
|
|
}
|
|
|
|
|
|
|
|
return max_dtr;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Handle the detection and initialisation of a card.
|
|
|
|
*
|
|
|
|
* In the case of a resume, "oldcard" will contain the card
|
|
|
|
* we're trying to reinitialise.
|
|
|
|
*/
|
|
|
|
static int mmc_sd_init_card(struct mmc_host *host, u32 ocr,
|
|
|
|
struct mmc_card *oldcard)
|
|
|
|
{
|
|
|
|
struct mmc_card *card;
|
|
|
|
int err;
|
|
|
|
u32 cid[4];
|
2011-05-04 23:48:59 -07:00
|
|
|
u32 rocr = 0;
|
2010-08-10 18:01:40 -07:00
|
|
|
|
|
|
|
WARN_ON(!host->claimed);
|
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
err = mmc_sd_get_cid(host, ocr, cid, &rocr);
|
2010-08-10 18:01:40 -07:00
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
if (oldcard) {
|
|
|
|
if (memcmp(cid, oldcard->raw_cid, sizeof(cid)) != 0)
|
|
|
|
return -ENOENT;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
card = oldcard;
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* Allocate card structure.
|
|
|
|
*/
|
2008-03-21 15:54:50 -07:00
|
|
|
card = mmc_alloc_card(host, &sd_type);
|
2010-08-10 18:01:40 -07:00
|
|
|
if (IS_ERR(card))
|
|
|
|
return PTR_ERR(card);
|
2007-05-01 07:00:02 -07:00
|
|
|
|
2013-09-13 02:31:33 -07:00
|
|
|
card->ocr = ocr;
|
2007-05-01 07:00:02 -07:00
|
|
|
card->type = MMC_TYPE_SD;
|
|
|
|
memcpy(card->raw_cid, cid, sizeof(card->raw_cid));
|
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2014-12-02 16:42:45 -07:00
|
|
|
/*
|
|
|
|
* Call the optional HC's init_card function to handle quirks.
|
|
|
|
*/
|
|
|
|
if (host->ops->init_card)
|
|
|
|
host->ops->init_card(host, card);
|
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
/*
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
* For native busses: get card RCA and quit open drain mode.
|
2006-12-30 16:11:32 -07:00
|
|
|
*/
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
if (!mmc_host_is_spi(host)) {
|
|
|
|
err = mmc_send_relative_addr(host, &card->rca);
|
|
|
|
if (err)
|
2013-07-16 23:21:10 -07:00
|
|
|
goto free_card;
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
if (!oldcard) {
|
2010-08-10 18:01:40 -07:00
|
|
|
err = mmc_sd_get_csd(host, card);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2013-07-16 23:21:10 -07:00
|
|
|
goto free_card;
|
2007-05-01 07:11:57 -07:00
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
mmc_decode_cid(card);
|
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2014-08-19 01:45:51 -07:00
|
|
|
/*
|
|
|
|
* handling only for cards supporting DSR and hosts requesting
|
|
|
|
* DSR configuration
|
|
|
|
*/
|
|
|
|
if (card->csd.dsr_imp && host->dsr_req)
|
|
|
|
mmc_set_dsr(host);
|
|
|
|
|
2006-12-30 16:11:32 -07:00
|
|
|
/*
|
2007-05-01 07:00:02 -07:00
|
|
|
* Select card, as all following commands rely on that.
|
2006-12-30 16:11:32 -07:00
|
|
|
*/
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
if (!mmc_host_is_spi(host)) {
|
|
|
|
err = mmc_select_card(card);
|
|
|
|
if (err)
|
2013-07-16 23:21:10 -07:00
|
|
|
goto free_card;
|
2007-05-01 07:00:02 -07:00
|
|
|
}
|
2007-05-01 05:46:08 -07:00
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
err = mmc_sd_setup_card(host, card, oldcard != NULL);
|
|
|
|
if (err)
|
|
|
|
goto free_card;
|
2009-04-07 06:48:16 -07:00
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
/* Initialization sequence for UHS-I cards */
|
|
|
|
if (rocr & SD_ROCR_S18A) {
|
|
|
|
err = mmc_sd_init_uhs_card(card);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2006-12-30 16:11:32 -07:00
|
|
|
goto free_card;
|
2011-05-04 23:48:59 -07:00
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* Attempt to change to high-speed (if supported)
|
|
|
|
*/
|
|
|
|
err = mmc_sd_switch_hs(card);
|
|
|
|
if (err > 0)
|
2014-04-23 01:07:35 -07:00
|
|
|
mmc_set_timing(card->host, MMC_TIMING_SD_HS);
|
2011-05-04 23:48:59 -07:00
|
|
|
else if (err)
|
|
|
|
goto free_card;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set bus speed.
|
|
|
|
*/
|
|
|
|
mmc_set_clock(host, mmc_sd_get_max_clock(card));
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2011-05-04 23:48:59 -07:00
|
|
|
/*
|
|
|
|
* Switch to wider bus (if supported).
|
|
|
|
*/
|
|
|
|
if ((host->caps & MMC_CAP_4_BIT_DATA) &&
|
|
|
|
(card->scr.bus_widths & SD_SCR_BUS_WIDTH_4)) {
|
|
|
|
err = mmc_app_set_bus_width(card, MMC_BUS_WIDTH_4);
|
|
|
|
if (err)
|
|
|
|
goto free_card;
|
|
|
|
|
|
|
|
mmc_set_bus_width(host, MMC_BUS_WIDTH_4);
|
|
|
|
}
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|
|
|
|
|
2010-08-10 18:01:40 -07:00
|
|
|
host->card = card;
|
2007-07-22 13:18:46 -07:00
|
|
|
return 0;
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
free_card:
|
|
|
|
if (!oldcard)
|
|
|
|
mmc_remove_card(card);
|
|
|
|
|
2007-07-22 14:08:30 -07:00
|
|
|
return err;
|
2007-05-01 07:00:02 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Host is being removed. Free up the current card.
|
|
|
|
*/
|
|
|
|
static void mmc_sd_remove(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
mmc_remove_card(host->card);
|
|
|
|
host->card = NULL;
|
|
|
|
}
|
|
|
|
|
2011-11-28 07:22:00 -07:00
|
|
|
/*
|
|
|
|
* Card detection - card is alive.
|
|
|
|
*/
|
|
|
|
static int mmc_sd_alive(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
return mmc_send_status(host->card, NULL);
|
|
|
|
}
|
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
/*
|
|
|
|
* Card detection callback from host.
|
|
|
|
*/
|
|
|
|
static void mmc_sd_detect(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
2013-05-02 05:02:38 -07:00
|
|
|
mmc_get_card(host->card);
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Just check if our card has been removed.
|
|
|
|
*/
|
2011-11-28 07:22:00 -07:00
|
|
|
err = _mmc_detect_card_removed(host);
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2013-05-02 05:02:38 -07:00
|
|
|
mmc_put_card(host->card);
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err) {
|
2007-05-19 04:39:01 -07:00
|
|
|
mmc_sd_remove(host);
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
mmc_claim_host(host);
|
|
|
|
mmc_detach_bus(host);
|
2011-09-21 11:08:13 -07:00
|
|
|
mmc_power_off(host);
|
2007-05-01 07:00:02 -07:00
|
|
|
mmc_release_host(host);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-10-10 05:20:05 -07:00
|
|
|
static int _mmc_sd_suspend(struct mmc_host *host)
|
2007-05-01 07:00:02 -07:00
|
|
|
{
|
2012-05-31 04:31:47 -07:00
|
|
|
int err = 0;
|
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
mmc_claim_host(host);
|
2013-10-02 08:37:09 -07:00
|
|
|
|
|
|
|
if (mmc_card_suspended(host->card))
|
|
|
|
goto out;
|
|
|
|
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
if (!mmc_host_is_spi(host))
|
2012-05-31 04:31:47 -07:00
|
|
|
err = mmc_deselect_cards(host);
|
2014-04-23 01:07:35 -07:00
|
|
|
|
2013-10-02 08:37:09 -07:00
|
|
|
if (!err) {
|
2013-06-10 08:03:38 -07:00
|
|
|
mmc_power_off(host);
|
2013-10-02 08:37:09 -07:00
|
|
|
mmc_card_set_suspended(host->card);
|
|
|
|
}
|
2009-09-22 16:45:29 -07:00
|
|
|
|
2013-10-02 08:37:09 -07:00
|
|
|
out:
|
|
|
|
mmc_release_host(host);
|
2012-05-31 04:31:47 -07:00
|
|
|
return err;
|
2007-05-01 07:00:02 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2013-10-10 05:20:05 -07:00
|
|
|
* Callback for suspend
|
|
|
|
*/
|
|
|
|
static int mmc_sd_suspend(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
err = _mmc_sd_suspend(host);
|
|
|
|
if (!err) {
|
|
|
|
pm_runtime_disable(&host->card->dev);
|
|
|
|
pm_runtime_set_suspended(&host->card->dev);
|
|
|
|
}
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-05-01 07:00:02 -07:00
|
|
|
* This function tries to determine if the same card is still present
|
|
|
|
* and, if so, restore all state to it.
|
|
|
|
*/
|
2013-10-10 05:20:05 -07:00
|
|
|
static int _mmc_sd_resume(struct mmc_host *host)
|
2007-05-01 07:00:02 -07:00
|
|
|
{
|
2013-10-02 08:37:09 -07:00
|
|
|
int err = 0;
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
mmc_claim_host(host);
|
2013-10-02 08:37:09 -07:00
|
|
|
|
|
|
|
if (!mmc_card_suspended(host->card))
|
|
|
|
goto out;
|
|
|
|
|
2013-09-13 02:31:33 -07:00
|
|
|
mmc_power_up(host, host->card->ocr);
|
|
|
|
err = mmc_sd_init_card(host, host->card->ocr, host->card);
|
2013-10-02 08:37:09 -07:00
|
|
|
mmc_card_clr_suspended(host->card);
|
2007-07-22 08:52:06 -07:00
|
|
|
|
2013-10-02 08:37:09 -07:00
|
|
|
out:
|
|
|
|
mmc_release_host(host);
|
2009-09-22 16:45:29 -07:00
|
|
|
return err;
|
2007-05-01 07:00:02 -07:00
|
|
|
}
|
|
|
|
|
2013-10-10 05:20:05 -07:00
|
|
|
/*
|
|
|
|
* Callback for resume
|
|
|
|
*/
|
|
|
|
static int mmc_sd_resume(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
pm_runtime_enable(&host->card->dev);
|
2015-11-05 08:01:32 -07:00
|
|
|
return 0;
|
2013-10-10 05:20:05 -07:00
|
|
|
}
|
|
|
|
|
2013-05-02 05:02:39 -07:00
|
|
|
/*
|
|
|
|
* Callback for runtime_suspend.
|
|
|
|
*/
|
|
|
|
static int mmc_sd_runtime_suspend(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (!(host->caps & MMC_CAP_AGGRESSIVE_PM))
|
|
|
|
return 0;
|
|
|
|
|
2013-10-10 05:20:05 -07:00
|
|
|
err = _mmc_sd_suspend(host);
|
2013-10-03 02:24:44 -07:00
|
|
|
if (err)
|
2015-02-24 07:11:26 -07:00
|
|
|
pr_err("%s: error %d doing aggressive suspend\n",
|
2013-05-02 05:02:39 -07:00
|
|
|
mmc_hostname(host), err);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Callback for runtime_resume.
|
|
|
|
*/
|
|
|
|
static int mmc_sd_runtime_resume(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
2013-10-10 05:20:05 -07:00
|
|
|
err = _mmc_sd_resume(host);
|
2015-12-14 06:51:27 -07:00
|
|
|
if (err && err != -ENOMEDIUM)
|
2015-11-05 08:01:32 -07:00
|
|
|
pr_err("%s: error %d doing runtime resume\n",
|
2013-05-02 05:02:39 -07:00
|
|
|
mmc_hostname(host), err);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2015-01-12 07:38:06 -07:00
|
|
|
static int mmc_sd_reset(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
mmc_power_cycle(host, host->card->ocr);
|
2015-06-01 02:14:58 -07:00
|
|
|
return mmc_sd_init_card(host, host->card->ocr, host->card);
|
2015-01-12 07:38:06 -07:00
|
|
|
}
|
|
|
|
|
2007-05-01 07:00:02 -07:00
|
|
|
static const struct mmc_bus_ops mmc_sd_ops = {
|
|
|
|
.remove = mmc_sd_remove,
|
|
|
|
.detect = mmc_sd_detect,
|
2013-05-02 05:02:39 -07:00
|
|
|
.runtime_suspend = mmc_sd_runtime_suspend,
|
|
|
|
.runtime_resume = mmc_sd_runtime_resume,
|
2007-05-01 07:00:02 -07:00
|
|
|
.suspend = mmc_sd_suspend,
|
|
|
|
.resume = mmc_sd_resume,
|
2011-11-28 07:22:00 -07:00
|
|
|
.alive = mmc_sd_alive,
|
2013-06-10 08:03:42 -07:00
|
|
|
.shutdown = mmc_sd_suspend,
|
2015-01-12 07:38:06 -07:00
|
|
|
.reset = mmc_sd_reset,
|
2007-05-01 07:00:02 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Starting point for SD card init.
|
|
|
|
*/
|
2011-01-03 11:36:56 -07:00
|
|
|
int mmc_attach_sd(struct mmc_host *host)
|
2007-05-01 07:00:02 -07:00
|
|
|
{
|
|
|
|
int err;
|
2013-09-13 02:31:33 -07:00
|
|
|
u32 ocr, rocr;
|
2007-05-01 07:00:02 -07:00
|
|
|
|
2007-08-09 04:23:56 -07:00
|
|
|
WARN_ON(!host->claimed);
|
2007-05-01 07:00:02 -07:00
|
|
|
|
2011-01-03 11:36:56 -07:00
|
|
|
err = mmc_send_app_op_cond(host, 0, &ocr);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
2013-10-29 17:00:18 -07:00
|
|
|
mmc_attach_bus(host, &mmc_sd_ops);
|
2010-12-08 02:04:30 -07:00
|
|
|
if (host->ocr_avail_sd)
|
|
|
|
host->ocr_avail = host->ocr_avail_sd;
|
2007-05-01 07:00:02 -07:00
|
|
|
|
MMC core learns about SPI
Teach the MMC/SD/SDIO core about using SPI mode.
- Use mmc_host_is_spi() so enumeration works through SPI signaling
and protocols, not just the native versions.
- Provide the SPI response type flags with each request issued,
including requests from the new lock/unlock code.
- Understand that cmd->resp[0] and mmc_get_status() results for SPI
return different values than for "native" MMC/SD protocol; this
affects resetting, checking card lock status, and some others.
- Understand that some commands act a bit differently ... notably:
* OP_COND command doesn't return the OCR
* APP_CMD status doesn't have an R1_APP_CMD analogue
Those changes required some new and updated primitives:
- Provide utilities to access two SPI-only requests, and one
request that wasn't previously needed:
* mmc_spi_read_ocr() ... SPI only
* mmc_spi_set_crc() ... SPI only (override by module parm)
* mmc_send_cid() ... for use without broadcast mode
- Updated internal routines:
* Previous mmc_send_csd() modified into mmc_send_cxd_native();
it uses native "R2" responses, which include 16 bytes of data.
* Previous mmc_send_ext_csd() becomes new mmc_send_cxd_data()
helper for command-and-data access
* Bugfix to that mmc_send_cxd_data() code: dma-to-stack is
unsafe/nonportable, so kmalloc a bounce buffer instead.
- Modified mmc_send_ext_csd() now uses mmc_send_cxd_data() helper
- Modified mmc_send_csd(), and new mmc_spi_send_cid(), routines use
those helper routines based on whether they're native or SPI
The newest categories of cards supported by the MMC stack aren't expected
to work yet with SPI: MMC or SD cards with over 4GB data, and SDIO.
All those cards support SPI mode, so eventually they should work too.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2007-08-08 09:11:32 -07:00
|
|
|
/*
|
|
|
|
* We need to get OCR a different way for SPI.
|
|
|
|
*/
|
|
|
|
if (mmc_host_is_spi(host)) {
|
|
|
|
mmc_go_idle(host);
|
|
|
|
|
|
|
|
err = mmc_spi_read_ocr(host, 0, &ocr);
|
|
|
|
if (err)
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
2013-09-13 02:31:33 -07:00
|
|
|
rocr = mmc_select_voltage(host, ocr);
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Can we support the voltage(s) of the card(s)?
|
|
|
|
*/
|
2013-09-13 02:31:33 -07:00
|
|
|
if (!rocr) {
|
2007-07-22 15:12:10 -07:00
|
|
|
err = -EINVAL;
|
2007-05-01 07:00:02 -07:00
|
|
|
goto err;
|
2007-07-22 15:12:10 -07:00
|
|
|
}
|
2007-05-01 07:00:02 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Detect and init the card.
|
|
|
|
*/
|
2013-09-13 02:31:33 -07:00
|
|
|
err = mmc_sd_init_card(host, rocr, NULL);
|
2007-07-22 13:18:46 -07:00
|
|
|
if (err)
|
2007-05-01 07:00:02 -07:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
mmc_release_host(host);
|
2007-05-19 04:39:01 -07:00
|
|
|
err = mmc_add_card(host->card);
|
2006-12-30 16:11:32 -07:00
|
|
|
if (err)
|
2007-07-22 08:52:06 -07:00
|
|
|
goto remove_card;
|
2006-12-30 16:11:32 -07:00
|
|
|
|
2015-10-14 13:53:03 -07:00
|
|
|
mmc_claim_host(host);
|
2006-12-30 16:11:32 -07:00
|
|
|
return 0;
|
|
|
|
|
2007-07-22 08:52:06 -07:00
|
|
|
remove_card:
|
2007-05-01 07:00:02 -07:00
|
|
|
mmc_remove_card(host->card);
|
2006-12-30 16:11:32 -07:00
|
|
|
host->card = NULL;
|
2007-07-22 08:52:06 -07:00
|
|
|
mmc_claim_host(host);
|
2006-12-30 16:11:32 -07:00
|
|
|
err:
|
|
|
|
mmc_detach_bus(host);
|
|
|
|
|
2011-10-10 23:14:09 -07:00
|
|
|
pr_err("%s: error %d whilst initialising SD card\n",
|
2007-07-22 15:12:10 -07:00
|
|
|
mmc_hostname(host), err);
|
|
|
|
|
2007-07-22 14:08:30 -07:00
|
|
|
return err;
|
2006-12-30 16:11:32 -07:00
|
|
|
}
|