Patch "mmc: longer timeout for long read time quirk" has been added to the 3.14-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
mmc: longer timeout for long read time quirk
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mmc-longer-timeout-for-long-read-time-quirk.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
32ecd320db39bcb007679ed42f283740641b81eaMon Sep 17 00:00:00 2001
From: Matt Gumbel <[email protected]>
Date: Fri, 20 May 2016 10:33:46 +0300
Subject: mmc: longer timeout for long read time quirk
From: Matt Gumbel <[email protected]>
commit 32ecd320db39bcb007679ed42f283740641b81ea upstream.
008GE0 Toshiba mmc in some Intel Baytrail tablets responds to MMC_SEND_EXT_CSD in 450-600ms.
This patch will...
() Increase the long read time quirk timeout from 300ms to 600ms. Original
author of that quirk says 300ms was only a guess and that the number may need to be raised in the future.
() Add this specific MMC to the quirk
--- drivers/mmc/card/block.c | 5 +++-- drivers/mmc/core/core.c | 4 ++-- 2 files changed, 5 insertions(+), 4 deletions(-)
drivers/mmc/card/block.c +3 -2
@@ -2352,11 +2352,12 @@ static const struct mmc_fixup blk_fixups MMC_QUIRK_BLK_NO_CMD23),/* -* Some Micron MMC cards needs longer data read timeout than -* indicated in CSD. +* Some MMC cards need longer data read timeout than indicated in CSD. */ MMC_FIXUP (CID_NAME_ANY ,CID_MANFID_MICRON ,0x200 , add_quirk_mmc,MMC_QUIRK_LONG_READ_TIME ), +MMC_FIXUP ("008GE0" ,CID_MANFID_TOSHIBA ,CID_OEMID_ANY , add_quirk_mmc, + MMC_QUIRK_LONG_READ_TIME),/* * On these Samsung MoviNAND parts, performing secure erase or
drivers/mmc/core/core.c +2 -2
@@ -822,11 +822,11 @@ void mmc_set_data_timeout(struct mmc_dat/* * Some cards require longer data read timeout than indicated in CSD. * Address this by setting the read timeout to a "reasonably high" -* value. For the cards tested, 300ms has proven enough. If necessary, +* value. For the cards tested, 600ms has proven enough. If necessary, * this value can be increased if other problematic cards require this. */ if (mmc_card_long_read_time (card) && data->flags &MMC_DATA_READ ) { - data->timeout_ns =300000000 ; + data->timeout_ns =600000000 ; data->timeout_clks =0 ; }
Patches currently in stable-queue which might be from [email protected] are
queue-3.14/mmc-longer-timeout-for-long-read-time-quirk.patch