From d1eed108bb500343f8c018e6e56ca2f294bd3a69 Mon Sep 17 00:00:00 2001 From: Gabor Juhos Date: Wed, 9 May 2012 11:38:39 +0000 Subject: kirkwood: nuke 2.6.37 support SVN-Revision: 31666 --- .../linux/kirkwood/patches/002-mvsdio_delay.patch | 32 ---------------------- 1 file changed, 32 deletions(-) delete mode 100644 target/linux/kirkwood/patches/002-mvsdio_delay.patch (limited to 'target/linux/kirkwood/patches/002-mvsdio_delay.patch') diff --git a/target/linux/kirkwood/patches/002-mvsdio_delay.patch b/target/linux/kirkwood/patches/002-mvsdio_delay.patch deleted file mode 100644 index ba28853604..0000000000 --- a/target/linux/kirkwood/patches/002-mvsdio_delay.patch +++ /dev/null @@ -1,32 +0,0 @@ ---- a/drivers/mmc/core/sd.c -+++ b/drivers/mmc/core/sd.c -@@ -332,6 +332,15 @@ int mmc_sd_switch_hs(struct mmc_card *ca - return -ENOMEM; - } - -+ /* -+ * Some SDHC cards, notably those with a Sandisk SD controller -+ * (also found in Kingston products) need a bit of slack -+ * before successfully handling the SWITCH command. So far, -+ * cards identifying themselves as "SD04G" and "SD08G" are -+ * affected -+ */ -+ udelay(1000); -+ - err = mmc_sd_switch(card, 1, 0, 1, status); - if (err) - goto out; ---- a/drivers/mmc/core/core.c -+++ b/drivers/mmc/core/core.c -@@ -303,9 +303,9 @@ void mmc_set_data_timeout(struct mmc_dat - * The limit is really 250 ms, but that is - * insufficient for some crappy cards. - */ -- limit_us = 300000; -+ limit_us = 500000; - else -- limit_us = 100000; -+ limit_us = 200000; - - /* - * SDHC cards always use these fixed values. -- cgit v1.2.3