2005-04-17 06:20:36 +08:00
|
|
|
/*
|
2007-02-28 22:33:10 +08:00
|
|
|
* linux/include/linux/mmc/core.h
|
2005-04-17 06:20:36 +08:00
|
|
|
*
|
|
|
|
|
* 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.
|
|
|
|
|
*/
|
2007-02-28 22:33:10 +08:00
|
|
|
#ifndef LINUX_MMC_CORE_H
|
|
|
|
|
#define LINUX_MMC_CORE_H
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
|
#include <linux/device.h>
|
|
|
|
|
|
|
|
|
|
struct request;
|
|
|
|
|
struct mmc_data;
|
|
|
|
|
struct mmc_request;
|
|
|
|
|
|
|
|
|
|
struct mmc_command {
|
|
|
|
|
u32 opcode;
|
|
|
|
|
u32 arg;
|
|
|
|
|
u32 resp[4];
|
|
|
|
|
unsigned int flags; /* expected response type */
|
2006-02-02 20:23:12 +08:00
|
|
|
#define MMC_RSP_PRESENT (1 << 0)
|
|
|
|
|
#define MMC_RSP_136 (1 << 1) /* 136 bit response */
|
|
|
|
|
#define MMC_RSP_CRC (1 << 2) /* expect valid crc */
|
|
|
|
|
#define MMC_RSP_BUSY (1 << 3) /* card may send busy */
|
|
|
|
|
#define MMC_RSP_OPCODE (1 << 4) /* response contains opcode */
|
2007-08-09 00:09:01 +08:00
|
|
|
|
|
|
|
|
#define MMC_CMD_MASK (3 << 5) /* non-SPI command type */
|
2006-02-02 20:23:12 +08:00
|
|
|
#define MMC_CMD_AC (0 << 5)
|
|
|
|
|
#define MMC_CMD_ADTC (1 << 5)
|
|
|
|
|
#define MMC_CMD_BC (2 << 5)
|
|
|
|
|
#define MMC_CMD_BCR (3 << 5)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-08-09 00:09:01 +08:00
|
|
|
#define MMC_RSP_SPI_S1 (1 << 7) /* one status byte */
|
|
|
|
|
#define MMC_RSP_SPI_S2 (1 << 8) /* second byte */
|
|
|
|
|
#define MMC_RSP_SPI_B4 (1 << 9) /* four data bytes */
|
|
|
|
|
#define MMC_RSP_SPI_BUSY (1 << 10) /* card may send busy */
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
2007-08-09 00:09:01 +08:00
|
|
|
* These are the native response types, and correspond to valid bit
|
2005-04-17 06:20:36 +08:00
|
|
|
* patterns of the above flags. One additional valid pattern
|
|
|
|
|
* is all zeros, which means we don't expect a response.
|
|
|
|
|
*/
|
2006-02-02 20:23:12 +08:00
|
|
|
#define MMC_RSP_NONE (0)
|
|
|
|
|
#define MMC_RSP_R1 (MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE)
|
|
|
|
|
#define MMC_RSP_R1B (MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE|MMC_RSP_BUSY)
|
|
|
|
|
#define MMC_RSP_R2 (MMC_RSP_PRESENT|MMC_RSP_136|MMC_RSP_CRC)
|
|
|
|
|
#define MMC_RSP_R3 (MMC_RSP_PRESENT)
|
2007-05-22 02:23:20 +08:00
|
|
|
#define MMC_RSP_R4 (MMC_RSP_PRESENT)
|
2007-05-23 02:25:21 +08:00
|
|
|
#define MMC_RSP_R5 (MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE)
|
2007-01-04 23:04:47 +08:00
|
|
|
#define MMC_RSP_R6 (MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE)
|
2007-01-04 22:57:32 +08:00
|
|
|
#define MMC_RSP_R7 (MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE)
|
2006-02-02 20:23:12 +08:00
|
|
|
|
|
|
|
|
#define mmc_resp_type(cmd) ((cmd)->flags & (MMC_RSP_PRESENT|MMC_RSP_136|MMC_RSP_CRC|MMC_RSP_BUSY|MMC_RSP_OPCODE))
|
|
|
|
|
|
2007-08-09 00:09:01 +08:00
|
|
|
/*
|
|
|
|
|
* These are the SPI response types for MMC, SD, and SDIO cards.
|
|
|
|
|
* Commands return R1, with maybe more info. Zero is an error type;
|
|
|
|
|
* callers must always provide the appropriate MMC_RSP_SPI_Rx flags.
|
|
|
|
|
*/
|
|
|
|
|
#define MMC_RSP_SPI_R1 (MMC_RSP_SPI_S1)
|
|
|
|
|
#define MMC_RSP_SPI_R1B (MMC_RSP_SPI_S1|MMC_RSP_SPI_BUSY)
|
|
|
|
|
#define MMC_RSP_SPI_R2 (MMC_RSP_SPI_S1|MMC_RSP_SPI_S2)
|
|
|
|
|
#define MMC_RSP_SPI_R3 (MMC_RSP_SPI_S1|MMC_RSP_SPI_B4)
|
|
|
|
|
#define MMC_RSP_SPI_R4 (MMC_RSP_SPI_S1|MMC_RSP_SPI_B4)
|
|
|
|
|
#define MMC_RSP_SPI_R5 (MMC_RSP_SPI_S1|MMC_RSP_SPI_S2)
|
|
|
|
|
#define MMC_RSP_SPI_R7 (MMC_RSP_SPI_S1|MMC_RSP_SPI_B4)
|
|
|
|
|
|
|
|
|
|
#define mmc_spi_resp_type(cmd) ((cmd)->flags & \
|
|
|
|
|
(MMC_RSP_SPI_S1|MMC_RSP_SPI_BUSY|MMC_RSP_SPI_S2|MMC_RSP_SPI_B4))
|
|
|
|
|
|
2006-02-02 20:23:12 +08:00
|
|
|
/*
|
|
|
|
|
* These are the command types.
|
|
|
|
|
*/
|
2006-02-18 04:23:29 +08:00
|
|
|
#define mmc_cmd_type(cmd) ((cmd)->flags & MMC_CMD_MASK)
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
unsigned int retries; /* max number of retries */
|
|
|
|
|
unsigned int error; /* command error */
|
|
|
|
|
|
2007-07-23 04:18:46 +08:00
|
|
|
/*
|
|
|
|
|
* Standard errno values are used for errors, but some have specific
|
|
|
|
|
* meaning in the MMC layer:
|
|
|
|
|
*
|
|
|
|
|
* ETIMEDOUT Card took too long to respond
|
|
|
|
|
* EILSEQ Basic format problem with the received or sent data
|
|
|
|
|
* (e.g. CRC check failed, incorrect opcode in response
|
|
|
|
|
* or bad end bit)
|
|
|
|
|
* EINVAL Request cannot be performed because of restrictions
|
|
|
|
|
* in hardware and/or the driver
|
|
|
|
|
* ENOMEDIUM Host can determine that the slot is empty and is
|
|
|
|
|
* actively failing requests
|
|
|
|
|
*/
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-04-12 05:13:41 +08:00
|
|
|
unsigned int cmd_timeout_ms; /* in milliseconds */
|
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-12 05:17:46 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
struct mmc_data *data; /* data segment associated with cmd */
|
2005-10-28 23:28:04 +08:00
|
|
|
struct mmc_request *mrq; /* associated request */
|
2005-04-17 06:20:36 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct mmc_data {
|
|
|
|
|
unsigned int timeout_ns; /* data timeout (in ns, max 80ms) */
|
|
|
|
|
unsigned int timeout_clks; /* data timeout (in clocks) */
|
2006-05-20 04:48:03 +08:00
|
|
|
unsigned int blksz; /* data block size */
|
2005-04-17 06:20:36 +08:00
|
|
|
unsigned int blocks; /* number of blocks */
|
|
|
|
|
unsigned int error; /* data error */
|
|
|
|
|
unsigned int flags;
|
|
|
|
|
|
|
|
|
|
#define MMC_DATA_WRITE (1 << 8)
|
|
|
|
|
#define MMC_DATA_READ (1 << 9)
|
|
|
|
|
#define MMC_DATA_STREAM (1 << 10)
|
|
|
|
|
|
|
|
|
|
unsigned int bytes_xfered;
|
|
|
|
|
|
|
|
|
|
struct mmc_command *stop; /* stop command */
|
2005-10-28 23:28:04 +08:00
|
|
|
struct mmc_request *mrq; /* associated request */
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
unsigned int sg_len; /* size of scatter list */
|
|
|
|
|
struct scatterlist *sg; /* I/O scatter list */
|
2011-07-02 00:55:22 +08:00
|
|
|
s32 host_cookie; /* host private data */
|
2005-04-17 06:20:36 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct mmc_request {
|
2011-05-24 04:06:36 +08:00
|
|
|
struct mmc_command *sbc; /* SET_BLOCK_COUNT for multiblock */
|
2005-04-17 06:20:36 +08:00
|
|
|
struct mmc_command *cmd;
|
|
|
|
|
struct mmc_data *data;
|
|
|
|
|
struct mmc_command *stop;
|
|
|
|
|
|
2011-07-02 00:55:22 +08:00
|
|
|
struct completion completion;
|
2005-04-17 06:20:36 +08:00
|
|
|
void (*done)(struct mmc_request *);/* completion function */
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct mmc_host;
|
|
|
|
|
struct mmc_card;
|
2011-07-02 00:55:22 +08:00
|
|
|
struct mmc_async_req;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-07-02 00:55:22 +08:00
|
|
|
extern struct mmc_async_req *mmc_start_req(struct mmc_host *,
|
|
|
|
|
struct mmc_async_req *, int *);
|
2011-10-18 13:26:42 +08:00
|
|
|
extern int mmc_interrupt_hpi(struct mmc_card *);
|
2007-07-12 02:22:11 +08:00
|
|
|
extern void mmc_wait_for_req(struct mmc_host *, struct mmc_request *);
|
2005-04-17 06:20:36 +08:00
|
|
|
extern int mmc_wait_for_cmd(struct mmc_host *, struct mmc_command *, int);
|
2011-04-27 06:56:29 +08:00
|
|
|
extern int mmc_app_cmd(struct mmc_host *, struct mmc_card *);
|
2006-12-25 05:46:55 +08:00
|
|
|
extern int mmc_wait_for_app_cmd(struct mmc_host *, struct mmc_card *,
|
2005-09-07 06:18:50 +08:00
|
|
|
struct mmc_command *, int);
|
2011-04-12 05:13:43 +08:00
|
|
|
extern int mmc_switch(struct mmc_card *, u8, u8, u8, unsigned int);
|
2005-04-17 06:20:36 +08: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-12 05:17:46 +08:00
|
|
|
#define MMC_ERASE_ARG 0x00000000
|
|
|
|
|
#define MMC_SECURE_ERASE_ARG 0x80000000
|
|
|
|
|
#define MMC_TRIM_ARG 0x00000001
|
2011-10-18 08:34:04 +08:00
|
|
|
#define MMC_DISCARD_ARG 0x00000003
|
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-12 05:17:46 +08:00
|
|
|
#define MMC_SECURE_TRIM1_ARG 0x80000001
|
|
|
|
|
#define MMC_SECURE_TRIM2_ARG 0x80008000
|
|
|
|
|
|
|
|
|
|
#define MMC_SECURE_ARGS 0x80000000
|
|
|
|
|
#define MMC_TRIM_ARGS 0x00008001
|
|
|
|
|
|
|
|
|
|
extern int mmc_erase(struct mmc_card *card, unsigned int from, unsigned int nr,
|
|
|
|
|
unsigned int arg);
|
|
|
|
|
extern int mmc_can_erase(struct mmc_card *card);
|
|
|
|
|
extern int mmc_can_trim(struct mmc_card *card);
|
2011-10-18 08:34:04 +08:00
|
|
|
extern int mmc_can_discard(struct mmc_card *card);
|
2011-10-14 13:15:48 +08:00
|
|
|
extern int mmc_can_sanitize(struct mmc_card *card);
|
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-12 05:17:46 +08:00
|
|
|
extern int mmc_can_secure_erase_trim(struct mmc_card *card);
|
|
|
|
|
extern int mmc_erase_group_aligned(struct mmc_card *card, unsigned int from,
|
|
|
|
|
unsigned int nr);
|
2011-06-28 22:16:02 +08:00
|
|
|
extern unsigned int mmc_calc_max_discard(struct mmc_card *card);
|
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-12 05:17:46 +08:00
|
|
|
|
2010-08-24 18:20:26 +08:00
|
|
|
extern int mmc_set_blocklen(struct mmc_card *card, unsigned int blocklen);
|
2011-08-29 21:42:11 +08:00
|
|
|
extern int mmc_hw_reset(struct mmc_host *host);
|
|
|
|
|
extern int mmc_hw_reset_check(struct mmc_host *host);
|
|
|
|
|
extern int mmc_can_reset(struct mmc_card *card);
|
2010-08-24 18:20:26 +08:00
|
|
|
|
2007-07-25 01:16:54 +08:00
|
|
|
extern void mmc_set_data_timeout(struct mmc_data *, const struct mmc_card *);
|
2008-06-28 18:52:45 +08:00
|
|
|
extern unsigned int mmc_align_data_size(struct mmc_card *, unsigned int);
|
2006-09-07 22:57:12 +08:00
|
|
|
|
2007-06-30 22:21:52 +08:00
|
|
|
extern int __mmc_claim_host(struct mmc_host *host, atomic_t *abort);
|
2005-04-17 06:20:36 +08:00
|
|
|
extern void mmc_release_host(struct mmc_host *host);
|
2011-03-09 16:11:02 +08:00
|
|
|
extern void mmc_do_release_host(struct mmc_host *host);
|
2009-09-23 07:44:30 +08:00
|
|
|
extern int mmc_try_claim_host(struct mmc_host *host);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-10-14 13:03:21 +08:00
|
|
|
extern int mmc_flush_cache(struct mmc_card *);
|
|
|
|
|
|
2011-11-28 22:22:00 +08:00
|
|
|
extern int mmc_detect_card_removed(struct mmc_host *host);
|
|
|
|
|
|
2007-06-30 22:21:52 +08:00
|
|
|
/**
|
|
|
|
|
* mmc_claim_host - exclusively claim a host
|
|
|
|
|
* @host: mmc host to claim
|
|
|
|
|
*
|
|
|
|
|
* Claim a host for a set of operations.
|
|
|
|
|
*/
|
|
|
|
|
static inline void mmc_claim_host(struct mmc_host *host)
|
|
|
|
|
{
|
|
|
|
|
__mmc_claim_host(host, NULL);
|
|
|
|
|
}
|
|
|
|
|
|
2008-11-27 03:54:17 +08:00
|
|
|
extern u32 mmc_vddrange_to_ocrmask(int vdd_min, int vdd_max);
|
|
|
|
|
|
2011-05-28 04:04:03 +08:00
|
|
|
#endif /* LINUX_MMC_CORE_H */
|