[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1423828368-18456-1-git-send-email-addy.ke@rock-chips.com>
Date: Fri, 13 Feb 2015 19:52:45 +0800
From: Addy Ke <addy.ke@...k-chips.com>
To: jh80.chung@...sung.com, ulf.hansson@...aro.org, olof@...om.net,
alim.akhtar@...il.com, a.hajda@...sung.com, dianders@...omium.org
Cc: heiko@...ech.de, cf@...k-chips.com, lintao@...k-chips.com,
huangtao@...k-chips.com, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
Addy Ke <addy.ke@...k-chips.com>
Subject: [PATCH v3 0/3] about data busy
patch 1: This patch can fix bug that controller is still data busy after
reset all blocks. After this patch, I still get data busy in
set_ios().
patch 2: This patch fix bug 'Timeout sending command'. After patch1 and
patch2, there is no mmc errors after:
cd /sys/bus/platform/drivers/dwmmc_rockchip
for i in $(seq 1 10000); do
echo "========================" $i
echo ff0c0000.dwmmc > unbind
sleep .5
echo ff0c0000.dwmmc > bind
sleep 2
done
patch3: This patch fix bug that there is data busy before sdio send CMD53.
But This patch is necessary for sd and mmc too.
Addy Ke (3):
mmc: dw_mmc: update clock after host reach a stable voltage
mmc: dw_mmc: fix bug that cause 'Timeout sending command'
mmc: dw_mmc: Don't start command while data busy
drivers/mmc/host/dw_mmc.c | 41 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 40 insertions(+), 1 deletion(-)
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists