2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2007-02-28 14:33:10 +00:00
|
|
|
* linux/drivers/mmc/core/core.c
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
|
|
|
* Copyright (C) 2003-2004 Russell King, All Rights Reserved.
|
2005-09-06 22:18:56 +00:00
|
|
|
* SD support Copyright (C) 2004 Ian Molton, All Rights Reserved.
|
2008-06-28 10:52:45 +00:00
|
|
|
* Copyright (C) 2005-2008 Pierre Ossman, All Rights Reserved.
|
2006-10-21 10:35:02 +00:00
|
|
|
* MMCv4 support Copyright (C) 2006 Philip Langdale, All Rights Reserved.
|
2005-04-16 22:20:36 +00: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.
|
|
|
|
*/
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/completion.h>
|
|
|
|
#include <linux/device.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/pagemap.h>
|
|
|
|
#include <linux/err.h>
|
2007-09-24 05:15:48 +00:00
|
|
|
#include <linux/leds.h>
|
2005-09-06 22:18:53 +00:00
|
|
|
#include <linux/scatterlist.h>
|
2008-11-26 19:54:17 +00:00
|
|
|
#include <linux/log2.h>
|
2009-03-11 11:30:43 +00:00
|
|
|
#include <linux/regulator/consumer.h>
|
2010-11-28 05:21:30 +00:00
|
|
|
#include <linux/pm_runtime.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
#include <linux/mmc/card.h>
|
|
|
|
#include <linux/mmc/host.h>
|
2006-12-24 21:46:55 +00:00
|
|
|
#include <linux/mmc/mmc.h>
|
|
|
|
#include <linux/mmc/sd.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-02-28 14:33:10 +00:00
|
|
|
#include "core.h"
|
2007-05-19 12:32:22 +00:00
|
|
|
#include "bus.h"
|
|
|
|
#include "host.h"
|
2007-05-26 11:48:18 +00:00
|
|
|
#include "sdio_bus.h"
|
2006-12-24 21:46:55 +00:00
|
|
|
|
|
|
|
#include "mmc_ops.h"
|
|
|
|
#include "sd_ops.h"
|
2007-05-21 18:23:20 +00:00
|
|
|
#include "sdio_ops.h"
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-05-19 12:32:22 +00:00
|
|
|
static struct workqueue_struct *workqueue;
|
|
|
|
|
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 16:11:32 +00:00
|
|
|
/*
|
|
|
|
* Enabling software CRCs on the data blocks can be a significant (30%)
|
|
|
|
* performance cost, and for other reasons may not always be desired.
|
|
|
|
* So we allow it it to be disabled.
|
|
|
|
*/
|
|
|
|
int use_spi_crc = 1;
|
|
|
|
module_param(use_spi_crc, bool, 0);
|
|
|
|
|
2009-12-15 02:01:29 +00:00
|
|
|
/*
|
|
|
|
* We normally treat cards as removed during suspend if they are not
|
|
|
|
* known to be on a non-removable bus, to avoid the risk of writing
|
|
|
|
* back data to a different card after resume. Allow this to be
|
|
|
|
* overridden if necessary.
|
|
|
|
*/
|
|
|
|
#ifdef CONFIG_MMC_UNSAFE_RESUME
|
|
|
|
int mmc_assume_removable;
|
|
|
|
#else
|
|
|
|
int mmc_assume_removable = 1;
|
|
|
|
#endif
|
2010-09-27 08:42:19 +00:00
|
|
|
EXPORT_SYMBOL(mmc_assume_removable);
|
2009-12-15 02:01:29 +00:00
|
|
|
module_param_named(removable, mmc_assume_removable, bool, 0644);
|
|
|
|
MODULE_PARM_DESC(
|
|
|
|
removable,
|
|
|
|
"MMC/SD cards are removable and may be removed during suspend");
|
|
|
|
|
2007-05-19 12:32:22 +00:00
|
|
|
/*
|
|
|
|
* Internal function. Schedule delayed work in the MMC work queue.
|
|
|
|
*/
|
|
|
|
static int mmc_schedule_delayed_work(struct delayed_work *work,
|
|
|
|
unsigned long delay)
|
|
|
|
{
|
|
|
|
return queue_delayed_work(workqueue, work, delay);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Internal function. Flush all scheduled work from the MMC work queue.
|
|
|
|
*/
|
|
|
|
static void mmc_flush_scheduled_work(void)
|
|
|
|
{
|
|
|
|
flush_workqueue(workqueue);
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/**
|
2006-05-04 12:51:45 +00:00
|
|
|
* mmc_request_done - finish processing an MMC request
|
|
|
|
* @host: MMC host which completed request
|
|
|
|
* @mrq: MMC request which request
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
|
|
|
* MMC drivers should call this function when they have completed
|
2006-05-04 12:51:45 +00:00
|
|
|
* their processing of a request.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
void mmc_request_done(struct mmc_host *host, struct mmc_request *mrq)
|
|
|
|
{
|
|
|
|
struct mmc_command *cmd = mrq->cmd;
|
2006-05-04 17:22:51 +00:00
|
|
|
int err = cmd->error;
|
|
|
|
|
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 16:11:32 +00:00
|
|
|
if (err && cmd->retries && mmc_host_is_spi(host)) {
|
|
|
|
if (cmd->resp[0] & R1_SPI_ILLEGAL_COMMAND)
|
|
|
|
cmd->retries = 0;
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
if (err && cmd->retries) {
|
2007-07-24 19:46:49 +00:00
|
|
|
pr_debug("%s: req failed (CMD%u): %d, retrying...\n",
|
|
|
|
mmc_hostname(host), cmd->opcode, err);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
cmd->retries--;
|
|
|
|
cmd->error = 0;
|
|
|
|
host->ops->request(host, mrq);
|
2007-07-24 19:46:49 +00:00
|
|
|
} else {
|
2007-09-24 05:15:48 +00:00
|
|
|
led_trigger_event(host->led, LED_OFF);
|
|
|
|
|
2007-07-24 19:46:49 +00:00
|
|
|
pr_debug("%s: req done (CMD%u): %d: %08x %08x %08x %08x\n",
|
|
|
|
mmc_hostname(host), cmd->opcode, err,
|
|
|
|
cmd->resp[0], cmd->resp[1],
|
|
|
|
cmd->resp[2], cmd->resp[3]);
|
|
|
|
|
|
|
|
if (mrq->data) {
|
|
|
|
pr_debug("%s: %d bytes transferred: %d\n",
|
|
|
|
mmc_hostname(host),
|
|
|
|
mrq->data->bytes_xfered, mrq->data->error);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mrq->stop) {
|
|
|
|
pr_debug("%s: (CMD%u): %d: %08x %08x %08x %08x\n",
|
|
|
|
mmc_hostname(host), mrq->stop->opcode,
|
|
|
|
mrq->stop->error,
|
|
|
|
mrq->stop->resp[0], mrq->stop->resp[1],
|
|
|
|
mrq->stop->resp[2], mrq->stop->resp[3]);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mrq->done)
|
|
|
|
mrq->done(mrq);
|
2010-11-09 02:36:50 +00:00
|
|
|
|
|
|
|
mmc_host_clk_gate(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_request_done);
|
|
|
|
|
2007-07-24 22:40:58 +00:00
|
|
|
static void
|
2005-04-16 22:20:36 +00:00
|
|
|
mmc_start_request(struct mmc_host *host, struct mmc_request *mrq)
|
|
|
|
{
|
2007-04-13 20:47:01 +00:00
|
|
|
#ifdef CONFIG_MMC_DEBUG
|
|
|
|
unsigned int i, sz;
|
2008-07-28 23:09:37 +00:00
|
|
|
struct scatterlist *sg;
|
2007-04-13 20:47:01 +00:00
|
|
|
#endif
|
|
|
|
|
2006-05-04 17:22:51 +00:00
|
|
|
pr_debug("%s: starting CMD%u arg %08x flags %08x\n",
|
|
|
|
mmc_hostname(host), mrq->cmd->opcode,
|
|
|
|
mrq->cmd->arg, mrq->cmd->flags);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-07-24 19:46:49 +00:00
|
|
|
if (mrq->data) {
|
|
|
|
pr_debug("%s: blksz %d blocks %d flags %08x "
|
|
|
|
"tsac %d ms nsac %d\n",
|
|
|
|
mmc_hostname(host), mrq->data->blksz,
|
|
|
|
mrq->data->blocks, mrq->data->flags,
|
2007-08-07 12:06:18 +00:00
|
|
|
mrq->data->timeout_ns / 1000000,
|
2007-07-24 19:46:49 +00:00
|
|
|
mrq->data->timeout_clks);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mrq->stop) {
|
|
|
|
pr_debug("%s: CMD%u arg %08x flags %08x\n",
|
|
|
|
mmc_hostname(host), mrq->stop->opcode,
|
|
|
|
mrq->stop->arg, mrq->stop->flags);
|
|
|
|
}
|
|
|
|
|
2006-12-26 14:11:23 +00:00
|
|
|
WARN_ON(!host->claimed);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
mrq->cmd->error = 0;
|
|
|
|
mrq->cmd->mrq = mrq;
|
|
|
|
if (mrq->data) {
|
2006-11-21 16:54:23 +00:00
|
|
|
BUG_ON(mrq->data->blksz > host->max_blk_size);
|
2006-11-21 16:55:45 +00:00
|
|
|
BUG_ON(mrq->data->blocks > host->max_blk_count);
|
|
|
|
BUG_ON(mrq->data->blocks * mrq->data->blksz >
|
|
|
|
host->max_req_size);
|
2006-11-21 16:54:23 +00:00
|
|
|
|
2007-04-13 20:47:01 +00:00
|
|
|
#ifdef CONFIG_MMC_DEBUG
|
|
|
|
sz = 0;
|
2008-07-28 23:09:37 +00:00
|
|
|
for_each_sg(mrq->data->sg, sg, mrq->data->sg_len, i)
|
|
|
|
sz += sg->length;
|
2007-04-13 20:47:01 +00:00
|
|
|
BUG_ON(sz != mrq->data->blocks * mrq->data->blksz);
|
|
|
|
#endif
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
mrq->cmd->data = mrq->data;
|
|
|
|
mrq->data->error = 0;
|
|
|
|
mrq->data->mrq = mrq;
|
|
|
|
if (mrq->stop) {
|
|
|
|
mrq->data->stop = mrq->stop;
|
|
|
|
mrq->stop->error = 0;
|
|
|
|
mrq->stop->mrq = mrq;
|
|
|
|
}
|
|
|
|
}
|
2010-11-09 02:36:50 +00:00
|
|
|
mmc_host_clk_ungate(host);
|
2011-02-06 18:02:48 +00:00
|
|
|
led_trigger_event(host->led, LED_FULL);
|
2005-04-16 22:20:36 +00:00
|
|
|
host->ops->request(host, mrq);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void mmc_wait_done(struct mmc_request *mrq)
|
|
|
|
{
|
|
|
|
complete(mrq->done_data);
|
|
|
|
}
|
|
|
|
|
2007-07-11 18:22:11 +00:00
|
|
|
/**
|
|
|
|
* mmc_wait_for_req - start a request and wait for completion
|
|
|
|
* @host: MMC host to start command
|
|
|
|
* @mrq: MMC request to start
|
|
|
|
*
|
|
|
|
* Start a new MMC custom command request for a host, and wait
|
|
|
|
* for the command to complete. Does not attempt to parse the
|
|
|
|
* response.
|
|
|
|
*/
|
|
|
|
void mmc_wait_for_req(struct mmc_host *host, struct mmc_request *mrq)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2006-07-03 07:25:35 +00:00
|
|
|
DECLARE_COMPLETION_ONSTACK(complete);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
mrq->done_data = &complete;
|
|
|
|
mrq->done = mmc_wait_done;
|
|
|
|
|
|
|
|
mmc_start_request(host, mrq);
|
|
|
|
|
|
|
|
wait_for_completion(&complete);
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_wait_for_req);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_wait_for_cmd - start a command and wait for completion
|
|
|
|
* @host: MMC host to start command
|
|
|
|
* @cmd: MMC command to start
|
|
|
|
* @retries: maximum number of retries
|
|
|
|
*
|
|
|
|
* Start a new MMC command for a host, and wait for the command
|
|
|
|
* to complete. Return any error that occurred while the command
|
|
|
|
* was executing. Do not attempt to parse the response.
|
|
|
|
*/
|
|
|
|
int mmc_wait_for_cmd(struct mmc_host *host, struct mmc_command *cmd, int retries)
|
|
|
|
{
|
2011-04-14 03:49:45 +00:00
|
|
|
struct mmc_request mrq = {0};
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-08-09 11:23:56 +00:00
|
|
|
WARN_ON(!host->claimed);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
memset(cmd->resp, 0, sizeof(cmd->resp));
|
|
|
|
cmd->retries = retries;
|
|
|
|
|
|
|
|
mrq.cmd = cmd;
|
|
|
|
cmd->data = NULL;
|
|
|
|
|
|
|
|
mmc_wait_for_req(host, &mrq);
|
|
|
|
|
|
|
|
return cmd->error;
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_wait_for_cmd);
|
|
|
|
|
2006-09-07 14:57:12 +00:00
|
|
|
/**
|
|
|
|
* mmc_set_data_timeout - set the timeout for a data command
|
|
|
|
* @data: data phase for command
|
|
|
|
* @card: the MMC card associated with the data transfer
|
2007-07-11 18:22:11 +00:00
|
|
|
*
|
|
|
|
* Computes the data timeout parameters according to the
|
|
|
|
* correct algorithm given the card type.
|
2006-09-07 14:57:12 +00:00
|
|
|
*/
|
2007-07-24 17:16:54 +00:00
|
|
|
void mmc_set_data_timeout(struct mmc_data *data, const struct mmc_card *card)
|
2006-09-07 14:57:12 +00:00
|
|
|
{
|
|
|
|
unsigned int mult;
|
|
|
|
|
2007-08-07 12:11:55 +00:00
|
|
|
/*
|
|
|
|
* SDIO cards only define an upper 1 s limit on access.
|
|
|
|
*/
|
|
|
|
if (mmc_card_sdio(card)) {
|
|
|
|
data->timeout_ns = 1000000000;
|
|
|
|
data->timeout_clks = 0;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2006-09-07 14:57:12 +00:00
|
|
|
/*
|
|
|
|
* SD cards use a 100 multiplier rather than 10
|
|
|
|
*/
|
|
|
|
mult = mmc_card_sd(card) ? 100 : 10;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Scale up the multiplier (and therefore the timeout) by
|
|
|
|
* the r2w factor for writes.
|
|
|
|
*/
|
2007-07-24 17:16:54 +00:00
|
|
|
if (data->flags & MMC_DATA_WRITE)
|
2006-09-07 14:57:12 +00:00
|
|
|
mult <<= card->csd.r2w_factor;
|
|
|
|
|
|
|
|
data->timeout_ns = card->csd.tacc_ns * mult;
|
|
|
|
data->timeout_clks = card->csd.tacc_clks * mult;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* SD cards also have an upper limit on the timeout.
|
|
|
|
*/
|
|
|
|
if (mmc_card_sd(card)) {
|
|
|
|
unsigned int timeout_us, limit_us;
|
|
|
|
|
|
|
|
timeout_us = data->timeout_ns / 1000;
|
2011-01-04 23:44:32 +00:00
|
|
|
if (mmc_host_clk_rate(card->host))
|
|
|
|
timeout_us += data->timeout_clks * 1000 /
|
|
|
|
(mmc_host_clk_rate(card->host) / 1000);
|
2006-09-07 14:57:12 +00:00
|
|
|
|
2007-07-24 17:16:54 +00:00
|
|
|
if (data->flags & MMC_DATA_WRITE)
|
2008-10-26 11:37:25 +00:00
|
|
|
/*
|
|
|
|
* The limit is really 250 ms, but that is
|
|
|
|
* insufficient for some crappy cards.
|
|
|
|
*/
|
|
|
|
limit_us = 300000;
|
2006-09-07 14:57:12 +00:00
|
|
|
else
|
|
|
|
limit_us = 100000;
|
|
|
|
|
2007-01-04 14:57:32 +00:00
|
|
|
/*
|
|
|
|
* SDHC cards always use these fixed values.
|
|
|
|
*/
|
|
|
|
if (timeout_us > limit_us || mmc_card_blockaddr(card)) {
|
2006-09-07 14:57:12 +00:00
|
|
|
data->timeout_ns = limit_us * 1000;
|
|
|
|
data->timeout_clks = 0;
|
|
|
|
}
|
|
|
|
}
|
2009-03-11 13:28:39 +00:00
|
|
|
/*
|
|
|
|
* Some cards need very high timeouts if driven in SPI mode.
|
|
|
|
* The worst observed timeout was 900ms after writing a
|
|
|
|
* continuous stream of data until the internal logic
|
|
|
|
* overflowed.
|
|
|
|
*/
|
|
|
|
if (mmc_host_is_spi(card->host)) {
|
|
|
|
if (data->flags & MMC_DATA_WRITE) {
|
|
|
|
if (data->timeout_ns < 1000000000)
|
|
|
|
data->timeout_ns = 1000000000; /* 1s */
|
|
|
|
} else {
|
|
|
|
if (data->timeout_ns < 100000000)
|
|
|
|
data->timeout_ns = 100000000; /* 100ms */
|
|
|
|
}
|
|
|
|
}
|
2006-09-07 14:57:12 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_set_data_timeout);
|
|
|
|
|
2008-06-28 10:52:45 +00:00
|
|
|
/**
|
|
|
|
* mmc_align_data_size - pads a transfer size to a more optimal value
|
|
|
|
* @card: the MMC card associated with the data transfer
|
|
|
|
* @sz: original transfer size
|
|
|
|
*
|
|
|
|
* Pads the original data size with a number of extra bytes in
|
|
|
|
* order to avoid controller bugs and/or performance hits
|
|
|
|
* (e.g. some controllers revert to PIO for certain sizes).
|
|
|
|
*
|
|
|
|
* Returns the improved size, which might be unmodified.
|
|
|
|
*
|
|
|
|
* Note that this function is only relevant when issuing a
|
|
|
|
* single scatter gather entry.
|
|
|
|
*/
|
|
|
|
unsigned int mmc_align_data_size(struct mmc_card *card, unsigned int sz)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* FIXME: We don't have a system for the controller to tell
|
|
|
|
* the core about its problems yet, so for now we just 32-bit
|
|
|
|
* align the size.
|
|
|
|
*/
|
|
|
|
sz = ((sz + 3) / 4) * 4;
|
|
|
|
|
|
|
|
return sz;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_align_data_size);
|
|
|
|
|
2009-09-22 23:44:29 +00:00
|
|
|
/**
|
|
|
|
* mmc_host_enable - enable a host.
|
|
|
|
* @host: mmc host to enable
|
|
|
|
*
|
|
|
|
* Hosts that support power saving can use the 'enable' and 'disable'
|
|
|
|
* methods to exit and enter power saving states. For more information
|
|
|
|
* see comments for struct mmc_host_ops.
|
|
|
|
*/
|
|
|
|
int mmc_host_enable(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
if (!(host->caps & MMC_CAP_DISABLE))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->en_dis_recurs)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->nesting_cnt++)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
cancel_delayed_work_sync(&host->disable);
|
|
|
|
|
|
|
|
if (host->enabled)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->ops->enable) {
|
|
|
|
int err;
|
|
|
|
|
|
|
|
host->en_dis_recurs = 1;
|
|
|
|
err = host->ops->enable(host);
|
|
|
|
host->en_dis_recurs = 0;
|
|
|
|
|
|
|
|
if (err) {
|
|
|
|
pr_debug("%s: enable error %d\n",
|
|
|
|
mmc_hostname(host), err);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
host->enabled = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_host_enable);
|
|
|
|
|
|
|
|
static int mmc_host_do_disable(struct mmc_host *host, int lazy)
|
|
|
|
{
|
|
|
|
if (host->ops->disable) {
|
|
|
|
int err;
|
|
|
|
|
|
|
|
host->en_dis_recurs = 1;
|
|
|
|
err = host->ops->disable(host, lazy);
|
|
|
|
host->en_dis_recurs = 0;
|
|
|
|
|
|
|
|
if (err < 0) {
|
|
|
|
pr_debug("%s: disable error %d\n",
|
|
|
|
mmc_hostname(host), err);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
if (err > 0) {
|
|
|
|
unsigned long delay = msecs_to_jiffies(err);
|
|
|
|
|
|
|
|
mmc_schedule_delayed_work(&host->disable, delay);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
host->enabled = 0;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_host_disable - disable a host.
|
|
|
|
* @host: mmc host to disable
|
|
|
|
*
|
|
|
|
* Hosts that support power saving can use the 'enable' and 'disable'
|
|
|
|
* methods to exit and enter power saving states. For more information
|
|
|
|
* see comments for struct mmc_host_ops.
|
|
|
|
*/
|
|
|
|
int mmc_host_disable(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (!(host->caps & MMC_CAP_DISABLE))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->en_dis_recurs)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (--host->nesting_cnt)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (!host->enabled)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
err = mmc_host_do_disable(host, 0);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_host_disable);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/**
|
2007-06-30 14:21:52 +00:00
|
|
|
* __mmc_claim_host - exclusively claim a host
|
2005-04-16 22:20:36 +00:00
|
|
|
* @host: mmc host to claim
|
2007-06-30 14:21:52 +00:00
|
|
|
* @abort: whether or not the operation should be aborted
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
2007-06-30 14:21:52 +00:00
|
|
|
* Claim a host for a set of operations. If @abort is non null and
|
|
|
|
* dereference a non-zero value then this will return prematurely with
|
|
|
|
* that non-zero value without acquiring the lock. Returns zero
|
|
|
|
* with the lock held otherwise.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2007-06-30 14:21:52 +00:00
|
|
|
int __mmc_claim_host(struct mmc_host *host, atomic_t *abort)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
DECLARE_WAITQUEUE(wait, current);
|
|
|
|
unsigned long flags;
|
2007-06-30 14:21:52 +00:00
|
|
|
int stop;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-07-11 18:28:02 +00:00
|
|
|
might_sleep();
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
add_wait_queue(&host->wq, &wait);
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
while (1) {
|
|
|
|
set_current_state(TASK_UNINTERRUPTIBLE);
|
2007-06-30 14:21:52 +00:00
|
|
|
stop = abort ? atomic_read(abort) : 0;
|
2009-09-22 23:44:30 +00:00
|
|
|
if (stop || !host->claimed || host->claimer == current)
|
2005-04-16 22:20:36 +00:00
|
|
|
break;
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
schedule();
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
}
|
|
|
|
set_current_state(TASK_RUNNING);
|
2009-09-22 23:44:30 +00:00
|
|
|
if (!stop) {
|
2007-06-30 14:21:52 +00:00
|
|
|
host->claimed = 1;
|
2009-09-22 23:44:30 +00:00
|
|
|
host->claimer = current;
|
|
|
|
host->claim_cnt += 1;
|
|
|
|
} else
|
2007-06-30 14:21:52 +00:00
|
|
|
wake_up(&host->wq);
|
2005-04-16 22:20:36 +00:00
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
remove_wait_queue(&host->wq, &wait);
|
2009-09-22 23:44:29 +00:00
|
|
|
if (!stop)
|
|
|
|
mmc_host_enable(host);
|
2007-06-30 14:21:52 +00:00
|
|
|
return stop;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2007-06-30 14:21:52 +00:00
|
|
|
EXPORT_SYMBOL(__mmc_claim_host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-09-22 23:44:30 +00:00
|
|
|
/**
|
|
|
|
* mmc_try_claim_host - try exclusively to claim a host
|
|
|
|
* @host: mmc host to claim
|
|
|
|
*
|
|
|
|
* Returns %1 if the host is claimed, %0 otherwise.
|
|
|
|
*/
|
|
|
|
int mmc_try_claim_host(struct mmc_host *host)
|
2009-09-22 23:44:29 +00:00
|
|
|
{
|
|
|
|
int claimed_host = 0;
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2009-09-22 23:44:30 +00:00
|
|
|
if (!host->claimed || host->claimer == current) {
|
2009-09-22 23:44:29 +00:00
|
|
|
host->claimed = 1;
|
2009-09-22 23:44:30 +00:00
|
|
|
host->claimer = current;
|
|
|
|
host->claim_cnt += 1;
|
2009-09-22 23:44:29 +00:00
|
|
|
claimed_host = 1;
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
return claimed_host;
|
|
|
|
}
|
2009-09-22 23:44:30 +00:00
|
|
|
EXPORT_SYMBOL(mmc_try_claim_host);
|
2009-09-22 23:44:29 +00:00
|
|
|
|
2011-03-09 08:11:02 +00:00
|
|
|
/**
|
|
|
|
* mmc_do_release_host - release a claimed host
|
|
|
|
* @host: mmc host to release
|
|
|
|
*
|
|
|
|
* If you successfully claimed a host, this function will
|
|
|
|
* release it again.
|
|
|
|
*/
|
|
|
|
void mmc_do_release_host(struct mmc_host *host)
|
2009-09-22 23:44:29 +00:00
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2009-09-22 23:44:30 +00:00
|
|
|
if (--host->claim_cnt) {
|
|
|
|
/* Release for nested claim */
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
} else {
|
|
|
|
host->claimed = 0;
|
|
|
|
host->claimer = NULL;
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
wake_up(&host->wq);
|
|
|
|
}
|
2009-09-22 23:44:29 +00:00
|
|
|
}
|
2011-03-09 08:11:02 +00:00
|
|
|
EXPORT_SYMBOL(mmc_do_release_host);
|
2009-09-22 23:44:29 +00:00
|
|
|
|
|
|
|
void mmc_host_deeper_disable(struct work_struct *work)
|
|
|
|
{
|
|
|
|
struct mmc_host *host =
|
|
|
|
container_of(work, struct mmc_host, disable.work);
|
|
|
|
|
|
|
|
/* If the host is claimed then we do not want to disable it anymore */
|
|
|
|
if (!mmc_try_claim_host(host))
|
|
|
|
return;
|
|
|
|
mmc_host_do_disable(host, 1);
|
|
|
|
mmc_do_release_host(host);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_host_lazy_disable - lazily disable a host.
|
|
|
|
* @host: mmc host to disable
|
|
|
|
*
|
|
|
|
* Hosts that support power saving can use the 'enable' and 'disable'
|
|
|
|
* methods to exit and enter power saving states. For more information
|
|
|
|
* see comments for struct mmc_host_ops.
|
|
|
|
*/
|
|
|
|
int mmc_host_lazy_disable(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
if (!(host->caps & MMC_CAP_DISABLE))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->en_dis_recurs)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (--host->nesting_cnt)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (!host->enabled)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (host->disable_delay) {
|
|
|
|
mmc_schedule_delayed_work(&host->disable,
|
|
|
|
msecs_to_jiffies(host->disable_delay));
|
|
|
|
return 0;
|
|
|
|
} else
|
|
|
|
return mmc_host_do_disable(host, 1);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_host_lazy_disable);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/**
|
|
|
|
* mmc_release_host - release a host
|
|
|
|
* @host: mmc host to release
|
|
|
|
*
|
|
|
|
* Release a MMC host, allowing others to claim the host
|
|
|
|
* for their operations.
|
|
|
|
*/
|
|
|
|
void mmc_release_host(struct mmc_host *host)
|
|
|
|
{
|
2007-08-09 11:23:56 +00:00
|
|
|
WARN_ON(!host->claimed);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-09-22 23:44:29 +00:00
|
|
|
mmc_host_lazy_disable(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-09-22 23:44:29 +00:00
|
|
|
mmc_do_release_host(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_release_host);
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
/*
|
|
|
|
* Internal function that does the actual ios call to the host driver,
|
|
|
|
* optionally printing some debug output.
|
|
|
|
*/
|
2006-05-04 17:22:51 +00:00
|
|
|
static inline void mmc_set_ios(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
struct mmc_ios *ios = &host->ios;
|
|
|
|
|
2007-02-18 11:07:47 +00:00
|
|
|
pr_debug("%s: clock %uHz busmode %u powermode %u cs %u Vdd %u "
|
|
|
|
"width %u timing %u\n",
|
2006-05-04 17:22:51 +00:00
|
|
|
mmc_hostname(host), ios->clock, ios->bus_mode,
|
|
|
|
ios->power_mode, ios->chip_select, ios->vdd,
|
2007-02-18 11:07:47 +00:00
|
|
|
ios->bus_width, ios->timing);
|
2007-01-04 14:57:32 +00:00
|
|
|
|
2010-11-09 02:36:50 +00:00
|
|
|
if (ios->clock > 0)
|
|
|
|
mmc_set_ungated(host);
|
2006-05-04 17:22:51 +00:00
|
|
|
host->ops->set_ios(host, ios);
|
|
|
|
}
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
/*
|
|
|
|
* Control chip select pin on a host.
|
|
|
|
*/
|
2006-12-24 21:46:55 +00:00
|
|
|
void mmc_set_chip_select(struct mmc_host *host, int mode)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2006-12-24 21:46:55 +00:00
|
|
|
host->ios.chip_select = mode;
|
|
|
|
mmc_set_ios(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
/*
|
|
|
|
* Sets the host clock to the highest possible frequency that
|
|
|
|
* is below "hz".
|
|
|
|
*/
|
|
|
|
void mmc_set_clock(struct mmc_host *host, unsigned int hz)
|
|
|
|
{
|
|
|
|
WARN_ON(hz < host->f_min);
|
|
|
|
|
|
|
|
if (hz > host->f_max)
|
|
|
|
hz = host->f_max;
|
|
|
|
|
|
|
|
host->ios.clock = hz;
|
|
|
|
mmc_set_ios(host);
|
|
|
|
}
|
|
|
|
|
2010-11-09 02:36:50 +00:00
|
|
|
#ifdef CONFIG_MMC_CLKGATE
|
|
|
|
/*
|
|
|
|
* This gates the clock by setting it to 0 Hz.
|
|
|
|
*/
|
|
|
|
void mmc_gate_clock(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->clk_lock, flags);
|
|
|
|
host->clk_old = host->ios.clock;
|
|
|
|
host->ios.clock = 0;
|
|
|
|
host->clk_gated = true;
|
|
|
|
spin_unlock_irqrestore(&host->clk_lock, flags);
|
|
|
|
mmc_set_ios(host);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This restores the clock from gating by using the cached
|
|
|
|
* clock value.
|
|
|
|
*/
|
|
|
|
void mmc_ungate_clock(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* We should previously have gated the clock, so the clock shall
|
|
|
|
* be 0 here! The clock may however be 0 during initialization,
|
|
|
|
* when some request operations are performed before setting
|
|
|
|
* the frequency. When ungate is requested in that situation
|
|
|
|
* we just ignore the call.
|
|
|
|
*/
|
|
|
|
if (host->clk_old) {
|
|
|
|
BUG_ON(host->ios.clock);
|
|
|
|
/* This call will also set host->clk_gated to false */
|
|
|
|
mmc_set_clock(host, host->clk_old);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void mmc_set_ungated(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We've been given a new frequency while the clock is gated,
|
|
|
|
* so make sure we regard this as ungating it.
|
|
|
|
*/
|
|
|
|
spin_lock_irqsave(&host->clk_lock, flags);
|
|
|
|
host->clk_gated = false;
|
|
|
|
spin_unlock_irqrestore(&host->clk_lock, flags);
|
|
|
|
}
|
|
|
|
|
|
|
|
#else
|
|
|
|
void mmc_set_ungated(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
/*
|
|
|
|
* Change the bus mode (open drain/push-pull) of a host.
|
|
|
|
*/
|
|
|
|
void mmc_set_bus_mode(struct mmc_host *host, unsigned int mode)
|
|
|
|
{
|
|
|
|
host->ios.bus_mode = mode;
|
|
|
|
mmc_set_ios(host);
|
|
|
|
}
|
|
|
|
|
2010-08-24 10:20:26 +00:00
|
|
|
/*
|
|
|
|
* Change data bus width of a host.
|
|
|
|
*/
|
|
|
|
void mmc_set_bus_width(struct mmc_host *host, unsigned int width)
|
|
|
|
{
|
2011-05-13 05:47:18 +00:00
|
|
|
host->ios.bus_width = width;
|
|
|
|
mmc_set_ios(host);
|
2010-08-24 10:20:26 +00:00
|
|
|
}
|
|
|
|
|
2008-11-26 19:54:17 +00:00
|
|
|
/**
|
|
|
|
* mmc_vdd_to_ocrbitnum - Convert a voltage to the OCR bit number
|
|
|
|
* @vdd: voltage (mV)
|
|
|
|
* @low_bits: prefer low bits in boundary cases
|
|
|
|
*
|
|
|
|
* This function returns the OCR bit number according to the provided @vdd
|
|
|
|
* value. If conversion is not possible a negative errno value returned.
|
|
|
|
*
|
|
|
|
* Depending on the @low_bits flag the function prefers low or high OCR bits
|
|
|
|
* on boundary voltages. For example,
|
|
|
|
* with @low_bits = true, 3300 mV translates to ilog2(MMC_VDD_32_33);
|
|
|
|
* with @low_bits = false, 3300 mV translates to ilog2(MMC_VDD_33_34);
|
|
|
|
*
|
|
|
|
* Any value in the [1951:1999] range translates to the ilog2(MMC_VDD_20_21).
|
|
|
|
*/
|
|
|
|
static int mmc_vdd_to_ocrbitnum(int vdd, bool low_bits)
|
|
|
|
{
|
|
|
|
const int max_bit = ilog2(MMC_VDD_35_36);
|
|
|
|
int bit;
|
|
|
|
|
|
|
|
if (vdd < 1650 || vdd > 3600)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (vdd >= 1650 && vdd <= 1950)
|
|
|
|
return ilog2(MMC_VDD_165_195);
|
|
|
|
|
|
|
|
if (low_bits)
|
|
|
|
vdd -= 1;
|
|
|
|
|
|
|
|
/* Base 2000 mV, step 100 mV, bit's base 8. */
|
|
|
|
bit = (vdd - 2000) / 100 + 8;
|
|
|
|
if (bit > max_bit)
|
|
|
|
return max_bit;
|
|
|
|
return bit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_vddrange_to_ocrmask - Convert a voltage range to the OCR mask
|
|
|
|
* @vdd_min: minimum voltage value (mV)
|
|
|
|
* @vdd_max: maximum voltage value (mV)
|
|
|
|
*
|
|
|
|
* This function returns the OCR mask bits according to the provided @vdd_min
|
|
|
|
* and @vdd_max values. If conversion is not possible the function returns 0.
|
|
|
|
*
|
|
|
|
* Notes wrt boundary cases:
|
|
|
|
* This function sets the OCR bits for all boundary voltages, for example
|
|
|
|
* [3300:3400] range is translated to MMC_VDD_32_33 | MMC_VDD_33_34 |
|
|
|
|
* MMC_VDD_34_35 mask.
|
|
|
|
*/
|
|
|
|
u32 mmc_vddrange_to_ocrmask(int vdd_min, int vdd_max)
|
|
|
|
{
|
|
|
|
u32 mask = 0;
|
|
|
|
|
|
|
|
if (vdd_max < vdd_min)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Prefer high bits for the boundary vdd_max values. */
|
|
|
|
vdd_max = mmc_vdd_to_ocrbitnum(vdd_max, false);
|
|
|
|
if (vdd_max < 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Prefer low bits for the boundary vdd_min values. */
|
|
|
|
vdd_min = mmc_vdd_to_ocrbitnum(vdd_min, true);
|
|
|
|
if (vdd_min < 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Fill the mask, from max bit to min bit. */
|
|
|
|
while (vdd_max >= vdd_min)
|
|
|
|
mask |= 1 << vdd_max--;
|
|
|
|
|
|
|
|
return mask;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_vddrange_to_ocrmask);
|
|
|
|
|
2009-03-11 11:30:43 +00:00
|
|
|
#ifdef CONFIG_REGULATOR
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_regulator_get_ocrmask - return mask of supported voltages
|
|
|
|
* @supply: regulator to use
|
|
|
|
*
|
|
|
|
* This returns either a negative errno, or a mask of voltages that
|
|
|
|
* can be provided to MMC/SD/SDIO devices using the specified voltage
|
|
|
|
* regulator. This would normally be called before registering the
|
|
|
|
* MMC host adapter.
|
|
|
|
*/
|
|
|
|
int mmc_regulator_get_ocrmask(struct regulator *supply)
|
|
|
|
{
|
|
|
|
int result = 0;
|
|
|
|
int count;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
count = regulator_count_voltages(supply);
|
|
|
|
if (count < 0)
|
|
|
|
return count;
|
|
|
|
|
|
|
|
for (i = 0; i < count; i++) {
|
|
|
|
int vdd_uV;
|
|
|
|
int vdd_mV;
|
|
|
|
|
|
|
|
vdd_uV = regulator_list_voltage(supply, i);
|
|
|
|
if (vdd_uV <= 0)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
vdd_mV = vdd_uV / 1000;
|
|
|
|
result |= mmc_vddrange_to_ocrmask(vdd_mV, vdd_mV);
|
|
|
|
}
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_regulator_get_ocrmask);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_regulator_set_ocr - set regulator to match host->ios voltage
|
2010-09-29 05:08:27 +00:00
|
|
|
* @mmc: the host to regulate
|
2009-03-11 11:30:43 +00:00
|
|
|
* @supply: regulator to use
|
2010-09-29 05:08:27 +00:00
|
|
|
* @vdd_bit: zero for power off, else a bit number (host->ios.vdd)
|
2009-03-11 11:30:43 +00:00
|
|
|
*
|
|
|
|
* Returns zero on success, else negative errno.
|
|
|
|
*
|
|
|
|
* MMC host drivers may use this to enable or disable a regulator using
|
|
|
|
* a particular supply voltage. This would normally be called from the
|
|
|
|
* set_ios() method.
|
|
|
|
*/
|
2010-09-29 05:08:27 +00:00
|
|
|
int mmc_regulator_set_ocr(struct mmc_host *mmc,
|
|
|
|
struct regulator *supply,
|
|
|
|
unsigned short vdd_bit)
|
2009-03-11 11:30:43 +00:00
|
|
|
{
|
|
|
|
int result = 0;
|
|
|
|
int min_uV, max_uV;
|
|
|
|
|
|
|
|
if (vdd_bit) {
|
|
|
|
int tmp;
|
|
|
|
int voltage;
|
|
|
|
|
|
|
|
/* REVISIT mmc_vddrange_to_ocrmask() may have set some
|
|
|
|
* bits this regulator doesn't quite support ... don't
|
|
|
|
* be too picky, most cards and regulators are OK with
|
|
|
|
* a 0.1V range goof (it's a small error percentage).
|
|
|
|
*/
|
|
|
|
tmp = vdd_bit - ilog2(MMC_VDD_165_195);
|
|
|
|
if (tmp == 0) {
|
|
|
|
min_uV = 1650 * 1000;
|
|
|
|
max_uV = 1950 * 1000;
|
|
|
|
} else {
|
|
|
|
min_uV = 1900 * 1000 + tmp * 100 * 1000;
|
|
|
|
max_uV = min_uV + 100 * 1000;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* avoid needless changes to this voltage; the regulator
|
|
|
|
* might not allow this operation
|
|
|
|
*/
|
|
|
|
voltage = regulator_get_voltage(supply);
|
|
|
|
if (voltage < 0)
|
|
|
|
result = voltage;
|
|
|
|
else if (voltage < min_uV || voltage > max_uV)
|
|
|
|
result = regulator_set_voltage(supply, min_uV, max_uV);
|
|
|
|
else
|
|
|
|
result = 0;
|
|
|
|
|
2010-09-29 05:08:27 +00:00
|
|
|
if (result == 0 && !mmc->regulator_enabled) {
|
2009-03-11 11:30:43 +00:00
|
|
|
result = regulator_enable(supply);
|
2010-09-29 05:08:27 +00:00
|
|
|
if (!result)
|
|
|
|
mmc->regulator_enabled = true;
|
|
|
|
}
|
|
|
|
} else if (mmc->regulator_enabled) {
|
2009-03-11 11:30:43 +00:00
|
|
|
result = regulator_disable(supply);
|
2010-09-29 05:08:27 +00:00
|
|
|
if (result == 0)
|
|
|
|
mmc->regulator_enabled = false;
|
2009-03-11 11:30:43 +00:00
|
|
|
}
|
|
|
|
|
2010-09-29 05:08:27 +00:00
|
|
|
if (result)
|
|
|
|
dev_err(mmc_dev(mmc),
|
|
|
|
"could not set regulator OCR (%d)\n", result);
|
2009-03-11 11:30:43 +00:00
|
|
|
return result;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_regulator_set_ocr);
|
|
|
|
|
2010-09-29 05:08:27 +00:00
|
|
|
#endif /* CONFIG_REGULATOR */
|
2009-03-11 11:30:43 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* Mask off any voltages we don't support and select
|
|
|
|
* the lowest voltage
|
|
|
|
*/
|
2006-12-30 23:11:32 +00:00
|
|
|
u32 mmc_select_voltage(struct mmc_host *host, u32 ocr)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
int bit;
|
|
|
|
|
|
|
|
ocr &= host->ocr_avail;
|
|
|
|
|
|
|
|
bit = ffs(ocr);
|
|
|
|
if (bit) {
|
|
|
|
bit -= 1;
|
|
|
|
|
2006-11-02 18:43:27 +00:00
|
|
|
ocr &= 3 << bit;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
host->ios.vdd = bit;
|
2006-05-04 17:22:51 +00:00
|
|
|
mmc_set_ios(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
} else {
|
2008-12-31 17:50:30 +00:00
|
|
|
pr_warning("%s: host doesn't support card's voltages\n",
|
|
|
|
mmc_hostname(host));
|
2005-04-16 22:20:36 +00:00
|
|
|
ocr = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return ocr;
|
|
|
|
}
|
|
|
|
|
2011-05-13 05:47:17 +00:00
|
|
|
int mmc_set_signal_voltage(struct mmc_host *host, int signal_voltage, bool cmd11)
|
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-05 06:48:57 +00:00
|
|
|
{
|
|
|
|
struct mmc_command cmd = {0};
|
|
|
|
int err = 0;
|
|
|
|
|
|
|
|
BUG_ON(!host);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Send CMD11 only if the request is to switch the card to
|
|
|
|
* 1.8V signalling.
|
|
|
|
*/
|
2011-05-13 05:47:17 +00:00
|
|
|
if ((signal_voltage != MMC_SIGNAL_VOLTAGE_330) && cmd11) {
|
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-05 06:48:57 +00:00
|
|
|
cmd.opcode = SD_SWITCH_VOLTAGE;
|
|
|
|
cmd.arg = 0;
|
|
|
|
cmd.flags = MMC_RSP_R1 | MMC_CMD_AC;
|
|
|
|
|
|
|
|
err = mmc_wait_for_cmd(host, &cmd, 0);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
if (!mmc_host_is_spi(host) && (cmd.resp[0] & R1_ERROR))
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
host->ios.signal_voltage = signal_voltage;
|
|
|
|
|
|
|
|
if (host->ops->start_signal_voltage_switch)
|
|
|
|
err = host->ops->start_signal_voltage_switch(host, &host->ios);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2005-09-06 22:18:53 +00:00
|
|
|
/*
|
2006-12-30 23:11:32 +00:00
|
|
|
* Select timing parameters for host.
|
2005-09-06 22:18:53 +00:00
|
|
|
*/
|
2006-12-30 23:11:32 +00:00
|
|
|
void mmc_set_timing(struct mmc_host *host, unsigned int timing)
|
2005-09-06 22:18:53 +00:00
|
|
|
{
|
2006-12-30 23:11:32 +00:00
|
|
|
host->ios.timing = timing;
|
|
|
|
mmc_set_ios(host);
|
2005-09-06 22:18:53 +00:00
|
|
|
}
|
|
|
|
|
2011-05-05 06:48:59 +00:00
|
|
|
/*
|
|
|
|
* Select appropriate driver type for host.
|
|
|
|
*/
|
|
|
|
void mmc_set_driver_type(struct mmc_host *host, unsigned int drv_type)
|
|
|
|
{
|
|
|
|
host->ios.drv_type = drv_type;
|
|
|
|
mmc_set_ios(host);
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2005-12-14 14:57:35 +00:00
|
|
|
* Apply power to the MMC stack. This is a two-stage process.
|
|
|
|
* First, we enable power to the card without the clock running.
|
|
|
|
* We then wait a bit for the power to stabilise. Finally,
|
|
|
|
* enable the bus drivers and clock to the card.
|
|
|
|
*
|
|
|
|
* We must _NOT_ enable the clock prior to power stablising.
|
|
|
|
*
|
|
|
|
* If a host does all the power sequencing itself, ignore the
|
|
|
|
* initial MMC_POWER_UP stage.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
static void mmc_power_up(struct mmc_host *host)
|
|
|
|
{
|
2009-09-22 23:44:18 +00:00
|
|
|
int bit;
|
|
|
|
|
|
|
|
/* If ocr is set, we use it */
|
|
|
|
if (host->ocr)
|
|
|
|
bit = ffs(host->ocr) - 1;
|
|
|
|
else
|
|
|
|
bit = fls(host->ocr_avail) - 1;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
host->ios.vdd = bit;
|
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 16:11:32 +00:00
|
|
|
if (mmc_host_is_spi(host)) {
|
|
|
|
host->ios.chip_select = MMC_CS_HIGH;
|
|
|
|
host->ios.bus_mode = MMC_BUSMODE_PUSHPULL;
|
|
|
|
} else {
|
|
|
|
host->ios.chip_select = MMC_CS_DONTCARE;
|
|
|
|
host->ios.bus_mode = MMC_BUSMODE_OPENDRAIN;
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
host->ios.power_mode = MMC_POWER_UP;
|
2005-09-06 22:18:55 +00:00
|
|
|
host->ios.bus_width = MMC_BUS_WIDTH_1;
|
2007-02-18 11:07:47 +00:00
|
|
|
host->ios.timing = MMC_TIMING_LEGACY;
|
2006-05-04 17:22:51 +00:00
|
|
|
mmc_set_ios(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-09-19 16:38:50 +00:00
|
|
|
/*
|
|
|
|
* This delay should be sufficient to allow the power supply
|
|
|
|
* to reach the minimum voltage.
|
|
|
|
*/
|
2009-03-10 01:21:21 +00:00
|
|
|
mmc_delay(10);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-09-06 01:37:19 +00:00
|
|
|
host->ios.clock = host->f_init;
|
2009-04-09 06:32:02 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
host->ios.power_mode = MMC_POWER_ON;
|
2006-05-04 17:22:51 +00:00
|
|
|
mmc_set_ios(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-09-19 16:38:50 +00:00
|
|
|
/*
|
|
|
|
* This delay must be at least 74 clock sizes, or 1 ms, or the
|
|
|
|
* time required to reach a stable voltage.
|
|
|
|
*/
|
2009-03-10 01:21:21 +00:00
|
|
|
mmc_delay(10);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void mmc_power_off(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
host->ios.clock = 0;
|
|
|
|
host->ios.vdd = 0;
|
2011-03-05 13:36:24 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Reset ocr mask to be the highest possible voltage supported for
|
|
|
|
* this mmc host. This value will be used at next power up.
|
|
|
|
*/
|
|
|
|
host->ocr = 1 << (fls(host->ocr_avail) - 1);
|
|
|
|
|
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 16:11:32 +00:00
|
|
|
if (!mmc_host_is_spi(host)) {
|
|
|
|
host->ios.bus_mode = MMC_BUSMODE_OPENDRAIN;
|
|
|
|
host->ios.chip_select = MMC_CS_DONTCARE;
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
host->ios.power_mode = MMC_POWER_OFF;
|
2005-09-06 22:18:55 +00:00
|
|
|
host->ios.bus_width = MMC_BUS_WIDTH_1;
|
2007-02-18 11:07:47 +00:00
|
|
|
host->ios.timing = MMC_TIMING_LEGACY;
|
2006-05-04 17:22:51 +00:00
|
|
|
mmc_set_ios(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2007-07-24 22:40:58 +00:00
|
|
|
/*
|
|
|
|
* Cleanup when the last reference to the bus operator is dropped.
|
|
|
|
*/
|
2008-04-13 18:15:47 +00:00
|
|
|
static void __mmc_release_bus(struct mmc_host *host)
|
2007-07-24 22:40:58 +00:00
|
|
|
{
|
|
|
|
BUG_ON(!host);
|
|
|
|
BUG_ON(host->bus_refs);
|
|
|
|
BUG_ON(!host->bus_dead);
|
|
|
|
|
|
|
|
host->bus_ops = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Increase reference count of bus operator
|
|
|
|
*/
|
|
|
|
static inline void mmc_bus_get(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
host->bus_refs++;
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Decrease reference count of bus operator and free it if
|
|
|
|
* it is the last reference.
|
|
|
|
*/
|
|
|
|
static inline void mmc_bus_put(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
host->bus_refs--;
|
|
|
|
if ((host->bus_refs == 0) && host->bus_ops)
|
|
|
|
__mmc_release_bus(host);
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2006-12-30 23:11:32 +00:00
|
|
|
* Assign a mmc bus handler to a host. Only one bus handler may control a
|
|
|
|
* host at any given time.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2006-12-30 23:11:32 +00:00
|
|
|
void mmc_attach_bus(struct mmc_host *host, const struct mmc_bus_ops *ops)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2006-12-30 23:11:32 +00:00
|
|
|
unsigned long flags;
|
2006-10-29 09:14:19 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
BUG_ON(!host);
|
|
|
|
BUG_ON(!ops);
|
2007-01-03 18:47:29 +00:00
|
|
|
|
2007-08-09 11:23:56 +00:00
|
|
|
WARN_ON(!host->claimed);
|
2006-10-21 10:35:02 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2006-10-21 10:35:02 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
BUG_ON(host->bus_ops);
|
|
|
|
BUG_ON(host->bus_refs);
|
2005-09-06 22:18:53 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
host->bus_ops = ops;
|
|
|
|
host->bus_refs = 1;
|
|
|
|
host->bus_dead = 0;
|
2005-09-06 22:18:53 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
2005-09-06 22:18:53 +00:00
|
|
|
}
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
/*
|
|
|
|
* Remove the current bus handler from a host. Assumes that there are
|
|
|
|
* no interesting cards left, so the bus is powered down.
|
|
|
|
*/
|
|
|
|
void mmc_detach_bus(struct mmc_host *host)
|
2006-11-08 22:03:10 +00:00
|
|
|
{
|
2006-12-30 23:11:32 +00:00
|
|
|
unsigned long flags;
|
2006-11-08 22:03:10 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
BUG_ON(!host);
|
2006-11-08 22:03:10 +00:00
|
|
|
|
2007-08-09 11:23:56 +00:00
|
|
|
WARN_ON(!host->claimed);
|
|
|
|
WARN_ON(!host->bus_ops);
|
2007-02-18 11:07:47 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2006-11-08 22:03:10 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
host->bus_dead = 1;
|
2006-11-08 22:03:10 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_power_off(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_put(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_detect_change - process change of state on a MMC socket
|
|
|
|
* @host: host which changed state.
|
2005-09-08 16:53:01 +00:00
|
|
|
* @delay: optional delay to wait before detection (jiffies)
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
2007-07-11 18:22:11 +00:00
|
|
|
* MMC drivers should call this when they detect a card has been
|
|
|
|
* inserted or removed. The MMC layer will confirm that any
|
|
|
|
* present card is still functional, and initialize any newly
|
|
|
|
* inserted.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2005-09-08 16:53:01 +00:00
|
|
|
void mmc_detect_change(struct mmc_host *host, unsigned long delay)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2007-02-11 19:43:19 +00:00
|
|
|
#ifdef CONFIG_MMC_DEBUG
|
2007-05-08 20:35:17 +00:00
|
|
|
unsigned long flags;
|
2007-05-09 09:32:34 +00:00
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2007-08-09 11:23:56 +00:00
|
|
|
WARN_ON(host->removed);
|
2007-05-09 09:32:34 +00:00
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
2007-02-11 19:43:19 +00:00
|
|
|
#endif
|
|
|
|
|
2006-11-22 14:57:56 +00:00
|
|
|
mmc_schedule_delayed_work(&host->detect, delay);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_detect_change);
|
|
|
|
|
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 21:17:46 +00:00
|
|
|
void mmc_init_erase(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
unsigned int sz;
|
|
|
|
|
|
|
|
if (is_power_of_2(card->erase_size))
|
|
|
|
card->erase_shift = ffs(card->erase_size) - 1;
|
|
|
|
else
|
|
|
|
card->erase_shift = 0;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* It is possible to erase an arbitrarily large area of an SD or MMC
|
|
|
|
* card. That is not desirable because it can take a long time
|
|
|
|
* (minutes) potentially delaying more important I/O, and also the
|
|
|
|
* timeout calculations become increasingly hugely over-estimated.
|
|
|
|
* Consequently, 'pref_erase' is defined as a guide to limit erases
|
|
|
|
* to that size and alignment.
|
|
|
|
*
|
|
|
|
* For SD cards that define Allocation Unit size, limit erases to one
|
|
|
|
* Allocation Unit at a time. For MMC cards that define High Capacity
|
|
|
|
* Erase Size, whether it is switched on or not, limit to that size.
|
|
|
|
* Otherwise just have a stab at a good value. For modern cards it
|
|
|
|
* will end up being 4MiB. Note that if the value is too small, it
|
|
|
|
* can end up taking longer to erase.
|
|
|
|
*/
|
|
|
|
if (mmc_card_sd(card) && card->ssr.au) {
|
|
|
|
card->pref_erase = card->ssr.au;
|
|
|
|
card->erase_shift = ffs(card->ssr.au) - 1;
|
|
|
|
} else if (card->ext_csd.hc_erase_size) {
|
|
|
|
card->pref_erase = card->ext_csd.hc_erase_size;
|
|
|
|
} else {
|
|
|
|
sz = (card->csd.capacity << (card->csd.read_blkbits - 9)) >> 11;
|
|
|
|
if (sz < 128)
|
|
|
|
card->pref_erase = 512 * 1024 / 512;
|
|
|
|
else if (sz < 512)
|
|
|
|
card->pref_erase = 1024 * 1024 / 512;
|
|
|
|
else if (sz < 1024)
|
|
|
|
card->pref_erase = 2 * 1024 * 1024 / 512;
|
|
|
|
else
|
|
|
|
card->pref_erase = 4 * 1024 * 1024 / 512;
|
|
|
|
if (card->pref_erase < card->erase_size)
|
|
|
|
card->pref_erase = card->erase_size;
|
|
|
|
else {
|
|
|
|
sz = card->pref_erase % card->erase_size;
|
|
|
|
if (sz)
|
|
|
|
card->pref_erase += card->erase_size - sz;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-04-11 21:13:41 +00:00
|
|
|
static unsigned int mmc_mmc_erase_timeout(struct mmc_card *card,
|
|
|
|
unsigned int arg, unsigned int qty)
|
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 21:17:46 +00:00
|
|
|
{
|
|
|
|
unsigned int erase_timeout;
|
|
|
|
|
|
|
|
if (card->ext_csd.erase_group_def & 1) {
|
|
|
|
/* High Capacity Erase Group Size uses HC timeouts */
|
|
|
|
if (arg == MMC_TRIM_ARG)
|
|
|
|
erase_timeout = card->ext_csd.trim_timeout;
|
|
|
|
else
|
|
|
|
erase_timeout = card->ext_csd.hc_erase_timeout;
|
|
|
|
} else {
|
|
|
|
/* CSD Erase Group Size uses write timeout */
|
|
|
|
unsigned int mult = (10 << card->csd.r2w_factor);
|
|
|
|
unsigned int timeout_clks = card->csd.tacc_clks * mult;
|
|
|
|
unsigned int timeout_us;
|
|
|
|
|
|
|
|
/* Avoid overflow: e.g. tacc_ns=80000000 mult=1280 */
|
|
|
|
if (card->csd.tacc_ns < 1000000)
|
|
|
|
timeout_us = (card->csd.tacc_ns * mult) / 1000;
|
|
|
|
else
|
|
|
|
timeout_us = (card->csd.tacc_ns / 1000) * mult;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ios.clock is only a target. The real clock rate might be
|
|
|
|
* less but not that much less, so fudge it by multiplying by 2.
|
|
|
|
*/
|
|
|
|
timeout_clks <<= 1;
|
|
|
|
timeout_us += (timeout_clks * 1000) /
|
|
|
|
(card->host->ios.clock / 1000);
|
|
|
|
|
|
|
|
erase_timeout = timeout_us / 1000;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Theoretically, the calculation could underflow so round up
|
|
|
|
* to 1ms in that case.
|
|
|
|
*/
|
|
|
|
if (!erase_timeout)
|
|
|
|
erase_timeout = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Multiplier for secure operations */
|
|
|
|
if (arg & MMC_SECURE_ARGS) {
|
|
|
|
if (arg == MMC_SECURE_ERASE_ARG)
|
|
|
|
erase_timeout *= card->ext_csd.sec_erase_mult;
|
|
|
|
else
|
|
|
|
erase_timeout *= card->ext_csd.sec_trim_mult;
|
|
|
|
}
|
|
|
|
|
|
|
|
erase_timeout *= qty;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Ensure at least a 1 second timeout for SPI as per
|
|
|
|
* 'mmc_set_data_timeout()'
|
|
|
|
*/
|
|
|
|
if (mmc_host_is_spi(card->host) && erase_timeout < 1000)
|
|
|
|
erase_timeout = 1000;
|
|
|
|
|
2011-04-11 21:13:41 +00:00
|
|
|
return erase_timeout;
|
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 21:17:46 +00:00
|
|
|
}
|
|
|
|
|
2011-04-11 21:13:41 +00:00
|
|
|
static unsigned int mmc_sd_erase_timeout(struct mmc_card *card,
|
|
|
|
unsigned int arg,
|
|
|
|
unsigned int qty)
|
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 21:17:46 +00:00
|
|
|
{
|
2011-04-11 21:13:41 +00:00
|
|
|
unsigned int erase_timeout;
|
|
|
|
|
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 21:17:46 +00:00
|
|
|
if (card->ssr.erase_timeout) {
|
|
|
|
/* Erase timeout specified in SD Status Register (SSR) */
|
2011-04-11 21:13:41 +00:00
|
|
|
erase_timeout = card->ssr.erase_timeout * qty +
|
|
|
|
card->ssr.erase_offset;
|
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 21:17:46 +00:00
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* Erase timeout not specified in SD Status Register (SSR) so
|
|
|
|
* use 250ms per write block.
|
|
|
|
*/
|
2011-04-11 21:13:41 +00:00
|
|
|
erase_timeout = 250 * qty;
|
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 21:17:46 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Must not be less than 1 second */
|
2011-04-11 21:13:41 +00:00
|
|
|
if (erase_timeout < 1000)
|
|
|
|
erase_timeout = 1000;
|
|
|
|
|
|
|
|
return erase_timeout;
|
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 21:17:46 +00:00
|
|
|
}
|
|
|
|
|
2011-04-11 21:13:41 +00:00
|
|
|
static unsigned int mmc_erase_timeout(struct mmc_card *card,
|
|
|
|
unsigned int arg,
|
|
|
|
unsigned int qty)
|
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 21:17:46 +00:00
|
|
|
{
|
|
|
|
if (mmc_card_sd(card))
|
2011-04-11 21:13:41 +00:00
|
|
|
return mmc_sd_erase_timeout(card, arg, qty);
|
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 21:17:46 +00:00
|
|
|
else
|
2011-04-11 21:13:41 +00:00
|
|
|
return mmc_mmc_erase_timeout(card, arg, qty);
|
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 21:17:46 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int mmc_do_erase(struct mmc_card *card, unsigned int from,
|
|
|
|
unsigned int to, unsigned int arg)
|
|
|
|
{
|
2011-04-14 03:40:30 +00:00
|
|
|
struct mmc_command cmd = {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 21:17:46 +00:00
|
|
|
unsigned int qty = 0;
|
|
|
|
int err;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* qty is used to calculate the erase timeout which depends on how many
|
|
|
|
* erase groups (or allocation units in SD terminology) are affected.
|
|
|
|
* We count erasing part of an erase group as one erase group.
|
|
|
|
* For SD, the allocation units are always a power of 2. For MMC, the
|
|
|
|
* erase group size is almost certainly also power of 2, but it does not
|
|
|
|
* seem to insist on that in the JEDEC standard, so we fall back to
|
|
|
|
* division in that case. SD may not specify an allocation unit size,
|
|
|
|
* in which case the timeout is based on the number of write blocks.
|
|
|
|
*
|
|
|
|
* Note that the timeout for secure trim 2 will only be correct if the
|
|
|
|
* number of erase groups specified is the same as the total of all
|
|
|
|
* preceding secure trim 1 commands. Since the power may have been
|
|
|
|
* lost since the secure trim 1 commands occurred, it is generally
|
|
|
|
* impossible to calculate the secure trim 2 timeout correctly.
|
|
|
|
*/
|
|
|
|
if (card->erase_shift)
|
|
|
|
qty += ((to >> card->erase_shift) -
|
|
|
|
(from >> card->erase_shift)) + 1;
|
|
|
|
else if (mmc_card_sd(card))
|
|
|
|
qty += to - from + 1;
|
|
|
|
else
|
|
|
|
qty += ((to / card->erase_size) -
|
|
|
|
(from / card->erase_size)) + 1;
|
|
|
|
|
|
|
|
if (!mmc_card_blockaddr(card)) {
|
|
|
|
from <<= 9;
|
|
|
|
to <<= 9;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mmc_card_sd(card))
|
|
|
|
cmd.opcode = SD_ERASE_WR_BLK_START;
|
|
|
|
else
|
|
|
|
cmd.opcode = MMC_ERASE_GROUP_START;
|
|
|
|
cmd.arg = from;
|
|
|
|
cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_AC;
|
|
|
|
err = mmc_wait_for_cmd(card->host, &cmd, 0);
|
|
|
|
if (err) {
|
|
|
|
printk(KERN_ERR "mmc_erase: group start error %d, "
|
|
|
|
"status %#x\n", err, cmd.resp[0]);
|
|
|
|
err = -EINVAL;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
memset(&cmd, 0, sizeof(struct mmc_command));
|
|
|
|
if (mmc_card_sd(card))
|
|
|
|
cmd.opcode = SD_ERASE_WR_BLK_END;
|
|
|
|
else
|
|
|
|
cmd.opcode = MMC_ERASE_GROUP_END;
|
|
|
|
cmd.arg = to;
|
|
|
|
cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_AC;
|
|
|
|
err = mmc_wait_for_cmd(card->host, &cmd, 0);
|
|
|
|
if (err) {
|
|
|
|
printk(KERN_ERR "mmc_erase: group end error %d, status %#x\n",
|
|
|
|
err, cmd.resp[0]);
|
|
|
|
err = -EINVAL;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
memset(&cmd, 0, sizeof(struct mmc_command));
|
|
|
|
cmd.opcode = MMC_ERASE;
|
|
|
|
cmd.arg = arg;
|
|
|
|
cmd.flags = MMC_RSP_SPI_R1B | MMC_RSP_R1B | MMC_CMD_AC;
|
2011-04-11 21:13:41 +00:00
|
|
|
cmd.cmd_timeout_ms = mmc_erase_timeout(card, arg, qty);
|
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 21:17:46 +00:00
|
|
|
err = mmc_wait_for_cmd(card->host, &cmd, 0);
|
|
|
|
if (err) {
|
|
|
|
printk(KERN_ERR "mmc_erase: erase error %d, status %#x\n",
|
|
|
|
err, cmd.resp[0]);
|
|
|
|
err = -EIO;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mmc_host_is_spi(card->host))
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
do {
|
|
|
|
memset(&cmd, 0, sizeof(struct mmc_command));
|
|
|
|
cmd.opcode = MMC_SEND_STATUS;
|
|
|
|
cmd.arg = card->rca << 16;
|
|
|
|
cmd.flags = MMC_RSP_R1 | MMC_CMD_AC;
|
|
|
|
/* Do not retry else we can't see errors */
|
|
|
|
err = mmc_wait_for_cmd(card->host, &cmd, 0);
|
|
|
|
if (err || (cmd.resp[0] & 0xFDF92000)) {
|
|
|
|
printk(KERN_ERR "error %d requesting status %#x\n",
|
|
|
|
err, cmd.resp[0]);
|
|
|
|
err = -EIO;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
} while (!(cmd.resp[0] & R1_READY_FOR_DATA) ||
|
|
|
|
R1_CURRENT_STATE(cmd.resp[0]) == 7);
|
|
|
|
out:
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_erase - erase sectors.
|
|
|
|
* @card: card to erase
|
|
|
|
* @from: first sector to erase
|
|
|
|
* @nr: number of sectors to erase
|
|
|
|
* @arg: erase command argument (SD supports only %MMC_ERASE_ARG)
|
|
|
|
*
|
|
|
|
* Caller must claim host before calling this function.
|
|
|
|
*/
|
|
|
|
int mmc_erase(struct mmc_card *card, unsigned int from, unsigned int nr,
|
|
|
|
unsigned int arg)
|
|
|
|
{
|
|
|
|
unsigned int rem, to = from + nr;
|
|
|
|
|
|
|
|
if (!(card->host->caps & MMC_CAP_ERASE) ||
|
|
|
|
!(card->csd.cmdclass & CCC_ERASE))
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
if (!card->erase_size)
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
if (mmc_card_sd(card) && arg != MMC_ERASE_ARG)
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
if ((arg & MMC_SECURE_ARGS) &&
|
|
|
|
!(card->ext_csd.sec_feature_support & EXT_CSD_SEC_ER_EN))
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
if ((arg & MMC_TRIM_ARGS) &&
|
|
|
|
!(card->ext_csd.sec_feature_support & EXT_CSD_SEC_GB_CL_EN))
|
|
|
|
return -EOPNOTSUPP;
|
|
|
|
|
|
|
|
if (arg == MMC_SECURE_ERASE_ARG) {
|
|
|
|
if (from % card->erase_size || nr % card->erase_size)
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (arg == MMC_ERASE_ARG) {
|
|
|
|
rem = from % card->erase_size;
|
|
|
|
if (rem) {
|
|
|
|
rem = card->erase_size - rem;
|
|
|
|
from += rem;
|
|
|
|
if (nr > rem)
|
|
|
|
nr -= rem;
|
|
|
|
else
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
rem = nr % card->erase_size;
|
|
|
|
if (rem)
|
|
|
|
nr -= rem;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (nr == 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
to = from + nr;
|
|
|
|
|
|
|
|
if (to <= from)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
/* 'from' and 'to' are inclusive */
|
|
|
|
to -= 1;
|
|
|
|
|
|
|
|
return mmc_do_erase(card, from, to, arg);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_erase);
|
|
|
|
|
|
|
|
int mmc_can_erase(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
if ((card->host->caps & MMC_CAP_ERASE) &&
|
|
|
|
(card->csd.cmdclass & CCC_ERASE) && card->erase_size)
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_can_erase);
|
|
|
|
|
|
|
|
int mmc_can_trim(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
if (card->ext_csd.sec_feature_support & EXT_CSD_SEC_GB_CL_EN)
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_can_trim);
|
|
|
|
|
|
|
|
int mmc_can_secure_erase_trim(struct mmc_card *card)
|
|
|
|
{
|
|
|
|
if (card->ext_csd.sec_feature_support & EXT_CSD_SEC_ER_EN)
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_can_secure_erase_trim);
|
|
|
|
|
|
|
|
int mmc_erase_group_aligned(struct mmc_card *card, unsigned int from,
|
|
|
|
unsigned int nr)
|
|
|
|
{
|
|
|
|
if (!card->erase_size)
|
|
|
|
return 0;
|
|
|
|
if (from % card->erase_size || nr % card->erase_size)
|
|
|
|
return 0;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_erase_group_aligned);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2010-08-24 10:20:26 +00:00
|
|
|
int mmc_set_blocklen(struct mmc_card *card, unsigned int blocklen)
|
|
|
|
{
|
2011-04-14 03:40:30 +00:00
|
|
|
struct mmc_command cmd = {0};
|
2010-08-24 10:20:26 +00:00
|
|
|
|
|
|
|
if (mmc_card_blockaddr(card) || mmc_card_ddr_mode(card))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
cmd.opcode = MMC_SET_BLOCKLEN;
|
|
|
|
cmd.arg = blocklen;
|
|
|
|
cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_AC;
|
|
|
|
return mmc_wait_for_cmd(card->host, &cmd, 5);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_set_blocklen);
|
|
|
|
|
2011-01-03 18:36:56 +00:00
|
|
|
static int mmc_rescan_try_freq(struct mmc_host *host, unsigned freq)
|
|
|
|
{
|
|
|
|
host->f_init = freq;
|
|
|
|
|
|
|
|
#ifdef CONFIG_MMC_DEBUG
|
|
|
|
pr_info("%s: %s: trying to init card at %u Hz\n",
|
|
|
|
mmc_hostname(host), __func__, host->f_init);
|
|
|
|
#endif
|
|
|
|
mmc_power_up(host);
|
2011-02-14 07:12:28 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* sdio_reset sends CMD52 to reset card. Since we do not know
|
|
|
|
* if the card is being re-initialized, just send it. CMD52
|
|
|
|
* should be ignored by SD/eMMC cards.
|
|
|
|
*/
|
2011-01-03 18:36:56 +00:00
|
|
|
sdio_reset(host);
|
|
|
|
mmc_go_idle(host);
|
|
|
|
|
|
|
|
mmc_send_if_cond(host, host->ocr_avail);
|
|
|
|
|
|
|
|
/* Order's important: probe SDIO, then SD, then MMC */
|
|
|
|
if (!mmc_attach_sdio(host))
|
|
|
|
return 0;
|
|
|
|
if (!mmc_attach_sd(host))
|
|
|
|
return 0;
|
|
|
|
if (!mmc_attach_mmc(host))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
mmc_power_off(host);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
2007-05-19 12:06:24 +00:00
|
|
|
void mmc_rescan(struct work_struct *work)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2011-01-03 18:36:56 +00:00
|
|
|
static const unsigned freqs[] = { 400000, 300000, 200000, 100000 };
|
2006-11-22 14:57:56 +00:00
|
|
|
struct mmc_host *host =
|
|
|
|
container_of(work, struct mmc_host, detect.work);
|
2010-09-06 01:37:19 +00:00
|
|
|
int i;
|
mmc: fix all hangs related to mmc/sd card insert/removal during suspend/resume
If you don't use CONFIG_MMC_UNSAFE_RESUME, as soon as you attempt to
suspend, the card will be removed, therefore this patch doesn't change the
behavior of this option.
However the removal will be done by pm notifier, which runs while
userspace is still not frozen and thus can freely use del_gendisk, without
the risk of deadlock which would happen otherwise.
Card detect workqueue is now disabled while userspace is frozen, Therefore
if you do use CONFIG_MMC_UNSAFE_RESUME, and remove the card during
suspend, the removal will be detected as soon as userspace is unfrozen,
again at the moment it is safe to call del_gendisk.
Tested with and without CONFIG_MMC_UNSAFE_RESUME with suspend and hibernate.
[akpm@linux-foundation.org: clean up function prototype]
[akpm@linux-foundation.org: fix CONFIG_PM-n linkage, small cleanups]
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Alan Stern <stern@rowland.harvard.edu>
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 01:01:41 +00:00
|
|
|
|
2011-01-03 18:36:56 +00:00
|
|
|
if (host->rescan_disable)
|
mmc: fix all hangs related to mmc/sd card insert/removal during suspend/resume
If you don't use CONFIG_MMC_UNSAFE_RESUME, as soon as you attempt to
suspend, the card will be removed, therefore this patch doesn't change the
behavior of this option.
However the removal will be done by pm notifier, which runs while
userspace is still not frozen and thus can freely use del_gendisk, without
the risk of deadlock which would happen otherwise.
Card detect workqueue is now disabled while userspace is frozen, Therefore
if you do use CONFIG_MMC_UNSAFE_RESUME, and remove the card during
suspend, the removal will be detected as soon as userspace is unfrozen,
again at the moment it is safe to call del_gendisk.
Tested with and without CONFIG_MMC_UNSAFE_RESUME with suspend and hibernate.
[akpm@linux-foundation.org: clean up function prototype]
[akpm@linux-foundation.org: fix CONFIG_PM-n linkage, small cleanups]
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Alan Stern <stern@rowland.harvard.edu>
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 01:01:41 +00:00
|
|
|
return;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_get(host);
|
2007-01-03 18:47:29 +00:00
|
|
|
|
2010-11-28 05:21:28 +00:00
|
|
|
/*
|
|
|
|
* if there is a _removable_ card registered, check whether it is
|
|
|
|
* still present
|
|
|
|
*/
|
|
|
|
if (host->bus_ops && host->bus_ops->detect && !host->bus_dead
|
2011-03-08 21:32:02 +00:00
|
|
|
&& !(host->caps & MMC_CAP_NONREMOVABLE))
|
2009-03-31 14:51:21 +00:00
|
|
|
host->bus_ops->detect(host);
|
|
|
|
|
2011-01-04 17:20:22 +00:00
|
|
|
/*
|
|
|
|
* Let mmc_bus_put() free the bus/bus_ops if we've found that
|
|
|
|
* the card is no longer present.
|
|
|
|
*/
|
2009-03-31 14:51:21 +00:00
|
|
|
mmc_bus_put(host);
|
|
|
|
mmc_bus_get(host);
|
|
|
|
|
|
|
|
/* if there still is a card present, stop here */
|
|
|
|
if (host->bus_ops != NULL) {
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_put(host);
|
2009-03-31 14:51:21 +00:00
|
|
|
goto out;
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-03-31 14:51:21 +00:00
|
|
|
/*
|
|
|
|
* Only we can add a new handler, so it's safe to
|
|
|
|
* release the lock here.
|
|
|
|
*/
|
|
|
|
mmc_bus_put(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-03-31 14:51:21 +00:00
|
|
|
if (host->ops->get_cd && host->ops->get_cd(host) == 0)
|
|
|
|
goto out;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-01-03 18:36:56 +00:00
|
|
|
mmc_claim_host(host);
|
2010-09-06 01:37:19 +00:00
|
|
|
for (i = 0; i < ARRAY_SIZE(freqs); i++) {
|
2011-01-03 18:36:56 +00:00
|
|
|
if (!mmc_rescan_try_freq(host, max(freqs[i], host->f_min)))
|
|
|
|
break;
|
2011-05-12 08:18:59 +00:00
|
|
|
if (freqs[i] <= host->f_min)
|
2011-01-03 18:36:56 +00:00
|
|
|
break;
|
2010-09-06 01:37:19 +00:00
|
|
|
}
|
2011-01-03 18:36:56 +00:00
|
|
|
mmc_release_host(host);
|
|
|
|
|
|
|
|
out:
|
2008-06-17 14:17:15 +00:00
|
|
|
if (host->caps & MMC_CAP_NEEDS_POLL)
|
|
|
|
mmc_schedule_delayed_work(&host->detect, HZ);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2007-05-19 12:06:24 +00:00
|
|
|
void mmc_start_host(struct mmc_host *host)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2007-05-19 12:06:24 +00:00
|
|
|
mmc_power_off(host);
|
|
|
|
mmc_detect_change(host, 0);
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
2007-05-19 12:06:24 +00:00
|
|
|
void mmc_stop_host(struct mmc_host *host)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2007-02-11 19:43:19 +00:00
|
|
|
#ifdef CONFIG_MMC_DEBUG
|
2007-05-08 20:35:17 +00:00
|
|
|
unsigned long flags;
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
2007-02-11 19:43:19 +00:00
|
|
|
host->removed = 1;
|
2007-05-08 20:35:17 +00:00
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
2007-02-11 19:43:19 +00:00
|
|
|
#endif
|
|
|
|
|
2009-09-22 23:44:29 +00:00
|
|
|
if (host->caps & MMC_CAP_DISABLE)
|
|
|
|
cancel_delayed_work(&host->disable);
|
2010-11-11 16:32:25 +00:00
|
|
|
cancel_delayed_work_sync(&host->detect);
|
2007-02-11 19:43:19 +00:00
|
|
|
mmc_flush_scheduled_work();
|
|
|
|
|
2010-03-05 21:43:31 +00:00
|
|
|
/* clear pm flags now and let card drivers set them as needed */
|
|
|
|
host->pm_flags = 0;
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_get(host);
|
|
|
|
if (host->bus_ops && !host->bus_dead) {
|
|
|
|
if (host->bus_ops->remove)
|
|
|
|
host->bus_ops->remove(host);
|
|
|
|
|
|
|
|
mmc_claim_host(host);
|
|
|
|
mmc_detach_bus(host);
|
|
|
|
mmc_release_host(host);
|
2009-09-22 23:44:36 +00:00
|
|
|
mmc_bus_put(host);
|
|
|
|
return;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_put(host);
|
|
|
|
|
|
|
|
BUG_ON(host->card);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
mmc_power_off(host);
|
|
|
|
}
|
|
|
|
|
2010-10-02 11:54:06 +00:00
|
|
|
int mmc_power_save_host(struct mmc_host *host)
|
2009-09-22 23:44:33 +00:00
|
|
|
{
|
2010-10-02 11:54:06 +00:00
|
|
|
int ret = 0;
|
|
|
|
|
2009-09-22 23:44:33 +00:00
|
|
|
mmc_bus_get(host);
|
|
|
|
|
|
|
|
if (!host->bus_ops || host->bus_dead || !host->bus_ops->power_restore) {
|
|
|
|
mmc_bus_put(host);
|
2010-10-02 11:54:06 +00:00
|
|
|
return -EINVAL;
|
2009-09-22 23:44:33 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
if (host->bus_ops->power_save)
|
2010-10-02 11:54:06 +00:00
|
|
|
ret = host->bus_ops->power_save(host);
|
2009-09-22 23:44:33 +00:00
|
|
|
|
|
|
|
mmc_bus_put(host);
|
|
|
|
|
|
|
|
mmc_power_off(host);
|
2010-10-02 11:54:06 +00:00
|
|
|
|
|
|
|
return ret;
|
2009-09-22 23:44:33 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_power_save_host);
|
|
|
|
|
2010-10-02 11:54:06 +00:00
|
|
|
int mmc_power_restore_host(struct mmc_host *host)
|
2009-09-22 23:44:33 +00:00
|
|
|
{
|
2010-10-02 11:54:06 +00:00
|
|
|
int ret;
|
|
|
|
|
2009-09-22 23:44:33 +00:00
|
|
|
mmc_bus_get(host);
|
|
|
|
|
|
|
|
if (!host->bus_ops || host->bus_dead || !host->bus_ops->power_restore) {
|
|
|
|
mmc_bus_put(host);
|
2010-10-02 11:54:06 +00:00
|
|
|
return -EINVAL;
|
2009-09-22 23:44:33 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
mmc_power_up(host);
|
2010-10-02 11:54:06 +00:00
|
|
|
ret = host->bus_ops->power_restore(host);
|
2009-09-22 23:44:33 +00:00
|
|
|
|
|
|
|
mmc_bus_put(host);
|
2010-10-02 11:54:06 +00:00
|
|
|
|
|
|
|
return ret;
|
2009-09-22 23:44:33 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_power_restore_host);
|
|
|
|
|
2009-09-22 23:44:34 +00:00
|
|
|
int mmc_card_awake(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err = -ENOSYS;
|
|
|
|
|
|
|
|
mmc_bus_get(host);
|
|
|
|
|
|
|
|
if (host->bus_ops && !host->bus_dead && host->bus_ops->awake)
|
|
|
|
err = host->bus_ops->awake(host);
|
|
|
|
|
|
|
|
mmc_bus_put(host);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_card_awake);
|
|
|
|
|
|
|
|
int mmc_card_sleep(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
int err = -ENOSYS;
|
|
|
|
|
|
|
|
mmc_bus_get(host);
|
|
|
|
|
|
|
|
if (host->bus_ops && !host->bus_dead && host->bus_ops->awake)
|
|
|
|
err = host->bus_ops->sleep(host);
|
|
|
|
|
|
|
|
mmc_bus_put(host);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_card_sleep);
|
|
|
|
|
|
|
|
int mmc_card_can_sleep(struct mmc_host *host)
|
|
|
|
{
|
|
|
|
struct mmc_card *card = host->card;
|
|
|
|
|
|
|
|
if (card && mmc_card_mmc(card) && card->ext_csd.rev >= 3)
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_card_can_sleep);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#ifdef CONFIG_PM
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_suspend_host - suspend a host
|
|
|
|
* @host: mmc host
|
|
|
|
*/
|
2010-05-26 21:42:08 +00:00
|
|
|
int mmc_suspend_host(struct mmc_host *host)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2009-09-22 23:45:29 +00:00
|
|
|
int err = 0;
|
|
|
|
|
2009-09-22 23:44:29 +00:00
|
|
|
if (host->caps & MMC_CAP_DISABLE)
|
|
|
|
cancel_delayed_work(&host->disable);
|
2009-02-19 11:17:03 +00:00
|
|
|
cancel_delayed_work(&host->detect);
|
2007-04-28 15:30:50 +00:00
|
|
|
mmc_flush_scheduled_work();
|
|
|
|
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_get(host);
|
|
|
|
if (host->bus_ops && !host->bus_dead) {
|
2007-05-01 14:00:02 +00:00
|
|
|
if (host->bus_ops->suspend)
|
2009-09-22 23:45:29 +00:00
|
|
|
err = host->bus_ops->suspend(host);
|
2010-10-13 07:31:56 +00:00
|
|
|
if (err == -ENOSYS || !host->bus_ops->resume) {
|
|
|
|
/*
|
|
|
|
* We simply "remove" the card in this case.
|
|
|
|
* It will be redetected on resume.
|
|
|
|
*/
|
|
|
|
if (host->bus_ops->remove)
|
|
|
|
host->bus_ops->remove(host);
|
|
|
|
mmc_claim_host(host);
|
|
|
|
mmc_detach_bus(host);
|
|
|
|
mmc_release_host(host);
|
|
|
|
host->pm_flags = 0;
|
|
|
|
err = 0;
|
|
|
|
}
|
2007-04-28 15:30:50 +00:00
|
|
|
}
|
2006-12-30 23:11:32 +00:00
|
|
|
mmc_bus_put(host);
|
|
|
|
|
2011-04-05 14:43:20 +00:00
|
|
|
if (!err && !mmc_card_keep_power(host))
|
2009-09-22 23:45:29 +00:00
|
|
|
mmc_power_off(host);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-09-22 23:45:29 +00:00
|
|
|
return err;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(mmc_suspend_host);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* mmc_resume_host - resume a previously suspended host
|
|
|
|
* @host: mmc host
|
|
|
|
*/
|
|
|
|
int mmc_resume_host(struct mmc_host *host)
|
|
|
|
{
|
2009-09-22 23:45:29 +00:00
|
|
|
int err = 0;
|
|
|
|
|
2007-05-01 14:00:02 +00:00
|
|
|
mmc_bus_get(host);
|
|
|
|
if (host->bus_ops && !host->bus_dead) {
|
2011-04-05 14:43:20 +00:00
|
|
|
if (!mmc_card_keep_power(host)) {
|
2010-03-05 21:43:31 +00:00
|
|
|
mmc_power_up(host);
|
|
|
|
mmc_select_voltage(host, host->ocr);
|
2010-11-28 05:21:30 +00:00
|
|
|
/*
|
|
|
|
* Tell runtime PM core we just powered up the card,
|
|
|
|
* since it still believes the card is powered off.
|
|
|
|
* Note that currently runtime PM is only enabled
|
|
|
|
* for SDIO cards that are MMC_CAP_POWER_OFF_CARD
|
|
|
|
*/
|
|
|
|
if (mmc_card_sdio(host->card) &&
|
|
|
|
(host->caps & MMC_CAP_POWER_OFF_CARD)) {
|
|
|
|
pm_runtime_disable(&host->card->dev);
|
|
|
|
pm_runtime_set_active(&host->card->dev);
|
|
|
|
pm_runtime_enable(&host->card->dev);
|
|
|
|
}
|
2010-03-05 21:43:31 +00:00
|
|
|
}
|
2007-05-01 14:00:02 +00:00
|
|
|
BUG_ON(!host->bus_ops->resume);
|
2009-09-22 23:45:29 +00:00
|
|
|
err = host->bus_ops->resume(host);
|
|
|
|
if (err) {
|
|
|
|
printk(KERN_WARNING "%s: error %d during resume "
|
|
|
|
"(card was removed?)\n",
|
|
|
|
mmc_hostname(host), err);
|
|
|
|
err = 0;
|
|
|
|
}
|
2007-05-01 14:00:02 +00:00
|
|
|
}
|
2011-05-09 08:32:31 +00:00
|
|
|
host->pm_flags &= ~MMC_PM_KEEP_POWER;
|
2007-05-01 14:00:02 +00:00
|
|
|
mmc_bus_put(host);
|
|
|
|
|
2009-09-22 23:45:29 +00:00
|
|
|
return err;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mmc_resume_host);
|
|
|
|
|
mmc: fix all hangs related to mmc/sd card insert/removal during suspend/resume
If you don't use CONFIG_MMC_UNSAFE_RESUME, as soon as you attempt to
suspend, the card will be removed, therefore this patch doesn't change the
behavior of this option.
However the removal will be done by pm notifier, which runs while
userspace is still not frozen and thus can freely use del_gendisk, without
the risk of deadlock which would happen otherwise.
Card detect workqueue is now disabled while userspace is frozen, Therefore
if you do use CONFIG_MMC_UNSAFE_RESUME, and remove the card during
suspend, the removal will be detected as soon as userspace is unfrozen,
again at the moment it is safe to call del_gendisk.
Tested with and without CONFIG_MMC_UNSAFE_RESUME with suspend and hibernate.
[akpm@linux-foundation.org: clean up function prototype]
[akpm@linux-foundation.org: fix CONFIG_PM-n linkage, small cleanups]
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Alan Stern <stern@rowland.harvard.edu>
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 01:01:41 +00:00
|
|
|
/* Do the card removal on suspend if card is assumed removeable
|
|
|
|
* Do that in pm notifier while userspace isn't yet frozen, so we will be able
|
|
|
|
to sync the card.
|
|
|
|
*/
|
|
|
|
int mmc_pm_notify(struct notifier_block *notify_block,
|
|
|
|
unsigned long mode, void *unused)
|
|
|
|
{
|
|
|
|
struct mmc_host *host = container_of(
|
|
|
|
notify_block, struct mmc_host, pm_notify);
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
|
|
|
|
switch (mode) {
|
|
|
|
case PM_HIBERNATION_PREPARE:
|
|
|
|
case PM_SUSPEND_PREPARE:
|
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
host->rescan_disable = 1;
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
cancel_delayed_work_sync(&host->detect);
|
|
|
|
|
|
|
|
if (!host->bus_ops || host->bus_ops->suspend)
|
|
|
|
break;
|
|
|
|
|
|
|
|
mmc_claim_host(host);
|
|
|
|
|
|
|
|
if (host->bus_ops->remove)
|
|
|
|
host->bus_ops->remove(host);
|
|
|
|
|
|
|
|
mmc_detach_bus(host);
|
|
|
|
mmc_release_host(host);
|
|
|
|
host->pm_flags = 0;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case PM_POST_SUSPEND:
|
|
|
|
case PM_POST_HIBERNATION:
|
2010-12-10 07:40:31 +00:00
|
|
|
case PM_POST_RESTORE:
|
mmc: fix all hangs related to mmc/sd card insert/removal during suspend/resume
If you don't use CONFIG_MMC_UNSAFE_RESUME, as soon as you attempt to
suspend, the card will be removed, therefore this patch doesn't change the
behavior of this option.
However the removal will be done by pm notifier, which runs while
userspace is still not frozen and thus can freely use del_gendisk, without
the risk of deadlock which would happen otherwise.
Card detect workqueue is now disabled while userspace is frozen, Therefore
if you do use CONFIG_MMC_UNSAFE_RESUME, and remove the card during
suspend, the removal will be detected as soon as userspace is unfrozen,
again at the moment it is safe to call del_gendisk.
Tested with and without CONFIG_MMC_UNSAFE_RESUME with suspend and hibernate.
[akpm@linux-foundation.org: clean up function prototype]
[akpm@linux-foundation.org: fix CONFIG_PM-n linkage, small cleanups]
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Alan Stern <stern@rowland.harvard.edu>
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 01:01:41 +00:00
|
|
|
|
|
|
|
spin_lock_irqsave(&host->lock, flags);
|
|
|
|
host->rescan_disable = 0;
|
|
|
|
spin_unlock_irqrestore(&host->lock, flags);
|
|
|
|
mmc_detect_change(host, 0);
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
#endif
|
|
|
|
|
2007-05-19 12:32:22 +00:00
|
|
|
static int __init mmc_init(void)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
2010-12-24 15:00:17 +00:00
|
|
|
workqueue = alloc_ordered_workqueue("kmmcd", 0);
|
2007-05-19 12:32:22 +00:00
|
|
|
if (!workqueue)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
ret = mmc_register_bus();
|
2007-05-26 11:48:18 +00:00
|
|
|
if (ret)
|
|
|
|
goto destroy_workqueue;
|
|
|
|
|
|
|
|
ret = mmc_register_host_class();
|
|
|
|
if (ret)
|
|
|
|
goto unregister_bus;
|
|
|
|
|
|
|
|
ret = sdio_register_bus();
|
|
|
|
if (ret)
|
|
|
|
goto unregister_host_class;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
unregister_host_class:
|
|
|
|
mmc_unregister_host_class();
|
|
|
|
unregister_bus:
|
|
|
|
mmc_unregister_bus();
|
|
|
|
destroy_workqueue:
|
|
|
|
destroy_workqueue(workqueue);
|
|
|
|
|
2007-05-19 12:32:22 +00:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit mmc_exit(void)
|
|
|
|
{
|
2007-05-26 11:48:18 +00:00
|
|
|
sdio_unregister_bus();
|
2007-05-19 12:32:22 +00:00
|
|
|
mmc_unregister_host_class();
|
|
|
|
mmc_unregister_bus();
|
|
|
|
destroy_workqueue(workqueue);
|
|
|
|
}
|
|
|
|
|
2007-06-16 06:07:53 +00:00
|
|
|
subsys_initcall(mmc_init);
|
2007-05-19 12:32:22 +00:00
|
|
|
module_exit(mmc_exit);
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
MODULE_LICENSE("GPL");
|