u-boot.git/drivers/mmc, branch v2015.01 Unnamed repository; edit this file 'description' to name the repository. MVEBUMMC : REMOVE unnecessary delay from init 2015-01-06T08:10:28+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:36+00:00 ac0b7298441d96043a2275d3c0fdafa59ca8f103 Remove unnessecary delay from mvebu_mmc_initialize Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Remove unnessecary delay from mvebu_mmc_initialize

Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
MVEBUMMC : CLEAN code 2015-01-06T08:10:23+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:35+00:00 02b2739e8fd90f3bc6945824d87ca1647cf95aef Clean mvebu_mmc_send_cmd Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Clean mvebu_mmc_send_cmd

Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
MVEBUMMC : REMOVE unnecessary delays 2015-01-06T08:10:16+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:34+00:00 86eeecafc24408822c1c8c329963e6f76751cae1 Remove delays in mvebu_mmc_set_bus and mvebu_mmc_set_clk Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Remove delays in mvebu_mmc_set_bus and mvebu_mmc_set_clk

Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
MVEBUMMC : FIX debug strings 2015-01-06T08:10:12+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:33+00:00 fc0f25f91948eef623999ab0874d6bd4604cb889 Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
MVEBUMMC : Speed up access time 2015-01-06T08:10:04+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:32+00:00 28d27b79e33dea24b0fb29cf7ff6e88dfb18f030 Get about 40x faster access on SHEEVAPLUG MMC Fix some SD type compatibility Changes in v3: - fix the HW_STATE (from linux mvsdio) - review delays and timeouts Changes in v2: - increase number of loops - remove initial delay Changes in v1: - review all loops, delays and timeouts Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Get about 40x faster access on SHEEVAPLUG MMC
 Fix some SD type compatibility

 Changes in v3:
 - fix the HW_STATE (from linux mvsdio)
 - review delays and timeouts

 Changes in v2:
 - increase number of loops
 - remove initial delay

 Changes in v1:
 - review all loops, delays and timeouts

Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
MVEBUMMC : Change copyright date 2015-01-06T08:09:45+00:00 Gerald Kerma drEagle@doukki.net 2014-12-13T20:35:31+00:00 2591fbdba3bbae92366d0a4f20fbaf4aa0f9f65c Signed-off-by: Gérald Kerma <drEagle@doukki.net> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> 
Signed-off-by: Gérald Kerma <drEagle@doukki.net>
Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com>
mmc: dw_mmc: Use active DDR mode flag 2014-12-12T19:09:01+00:00 Andrew Gabbasov andrew_gabbasov@mentor.com 2014-12-01T12:59:12+00:00 2b8a9692f9d8a744b6a93a9bed115ca46541ca1f The card_caps bit should denote the card capability to use DDR mode, but we need the flag indicating that the DDR mode is active. Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> 
The card_caps bit should denote the card capability to use DDR mode,
but we need the flag indicating that the DDR mode is active.

Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
mmc: Fix block length for DDR mode 2014-12-12T19:08:38+00:00 Andrew Gabbasov andrew_gabbasov@mentor.com 2014-12-01T12:59:11+00:00 5af8f45cd049cf01790a17ff68e61303bc08abc3 Block length for write and read commands is fixed to 512 bytes when the card is in Dual Data Rate mode. If block length read from CSD is different, make sure the driver will use correct length in all further calculations and settings. Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> 
Block length for write and read commands is fixed to 512 bytes
when the card is in Dual Data Rate mode. If block length read from CSD
is different, make sure the driver will use correct length
in all further calculations and settings.

Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
mmc: Fix Dual Data Rate capability recognition 2014-12-12T19:08:21+00:00 Andrew Gabbasov andrew_gabbasov@mentor.com 2014-12-01T12:59:10+00:00 201d5ac4388d66bf7a78e71c32939b3fc5779207 Since the driver doesn't work in 1.2V or 1.8V signaling level modes, Dual Data Rate mode can be supported by the driver only if it is supported by the card in regular 3.3V mode. So, check for a particular single bit in card type field. Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> 
Since the driver doesn't work in 1.2V or 1.8V signaling level modes,
Dual Data Rate mode can be supported by the driver only if it is supported
by the card in regular 3.3V mode. So, check for a particular single
bit in card type field.

Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
mmc: Fix handling of bus widths and DDR card capabilities 2014-12-12T19:08:06+00:00 Andrew Gabbasov andrew_gabbasov@mentor.com 2014-12-01T12:59:09+00:00 786e8f818c25265d12d5d06e257fe2b1ba516134 If the MMC_MODE_DDR_52MHz flag is set in card capabilities bitmask, it is never cleared, even if switching to DDR mode fails, and if the controller driver uses this flag to check the DDR mode, it can take incorrect actions. Also, DDR related checks in mmc_startup() incorrectly handle the case when the host controller does not support some bus widths (e.g. can't support 8 bits), since the host_caps is checked for DDR bit, but not bus width bits. This fix clearly separates using of card_caps bitmask, having there the flags for the capabilities, that the card can support, and actual operation mode, described outside of card_caps (i.e. bus_width and ddr_mode fields in mmc structure). Separate host controller drivers may need to be updated to use the actual flags. Respectively, the capabilities checks in mmc_startup are made more correct and clear. Also, some clean up is made with errors handling and code syntax layout. Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> 
If the MMC_MODE_DDR_52MHz flag is set in card capabilities bitmask,
it is never cleared, even if switching to DDR mode fails, and if
the controller driver uses this flag to check the DDR mode, it can
take incorrect actions.

Also, DDR related checks in mmc_startup() incorrectly handle the case
when the host controller does not support some bus widths (e.g. can't
support 8 bits), since the host_caps is checked for DDR bit, but not
bus width bits.

This fix clearly separates using of card_caps bitmask, having there
the flags for the capabilities, that the card can support, and actual
operation mode, described outside of card_caps (i.e. bus_width and
ddr_mode fields in mmc structure). Separate host controller drivers
may need to be updated to use the actual flags. Respectively,
the capabilities checks in mmc_startup are made more correct and clear.

Also, some clean up is made with errors handling and code syntax layout.

Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>