Hello everybody,
is there a safe combination of parameters for sdhci.debug_quirks and
sdhci.debug_quirks2 which should work in all cases, sacrificing performance?
regards,
Simon
Am 02.02.2015 um 15:06 schrieb Sébastien Bourdeauducq:
On 02/02/2015 09:38 PM, Simon Raffeiner (SCC) wrote:
I am
On 2015.02.09 12:51, Ulf Hansson wrote:
On 5 February 2015 at 12:13, Addy Ke addy...@rock-chips.com wrote:
Because of some uncertain factors, such as worse card or worse hardware,
DAT[3:0](the data lines) may be pulled down by card, and mmc controller
will be in busy state. This should not
On 02/09/2015 03:56 PM, Addy wrote:
On 2015.02.09 12:51, Ulf Hansson wrote:
On 5 February 2015 at 12:13, Addy Ke addy...@rock-chips.com wrote:
Because of some uncertain factors, such as worse card or worse hardware,
DAT[3:0](the data lines) may be pulled down by card, and mmc controller
Addy Ke (2):
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 | 35 +++
1 file changed, 35 insertions(+)
--
Changes in v2:
- add new patch to handle data busy when start
We should wait for data busy here in non-volt-switch state.
This may happend when sdio sends CMD53.
Signed-off-by: Addy Ke addy...@rock-chips.com
---
drivers/mmc/host/dw_mmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
index
Because of some uncertain factors, such as worse card or worse hardware,
DAT[3:0](the data lines) may be pulled down by card, and mmc controller
will be in busy state. This should not happend when mmc controller
send command to update card clocks. If this happends, mci_send_cmd will
be failed and
hi Chris, Ulf,
According to
https://www.sdcard.org/downloads/pls/simplified_specs/archive/partE1_200.pdf
(section CMD52 During Data Transfer ),
A card may accept CMD52 during data transfer if it supports Direct
Commands (see SDC, Table 6-3). For both SD and SPI modes, if an error
occurs during
On 5 February 2015 at 12:13, Addy Ke addy...@rock-chips.com wrote:
Because of some uncertain factors, such as worse card or worse hardware,
DAT[3:0](the data lines) may be pulled down by card, and mmc controller
will be in busy state. This should not happend when mmc controller
send command
