Skip to content
Snippets Groups Projects
Forked from Reform / reform-boundary-uboot
Source project has a limited visibility.
  • Jason Liu's avatar
    4571de33
    fsl_esdhc: Fix multi-block read restriction on i.MX53 eSDHCv2 · 4571de33
    Jason Liu authored
    
    For freescale i.MX53 eSDHCv2, when using CMD12, cmdtype need
    to be set to ABORT, otherwise, next read command will hang.
    
    This is a software Software Restrictions in i.MX53 reference manual:
    
    29.7.8 Multi-block Read
    For pre-defined multi-block read operation, that is,the number of blocks
    to read has been defined by previous CMD23 for MMC, or pre-defined number
    of blocks in CMD53 for SDIO/SDCombo,or whatever multi-block read without
    abort command at card side, an abort command, either automatic or manual
    CMD12/CMD52, is still required by ESDHC after the pre-defined number of
    blocks are done, to drive the internal state machine to idle mode. In this
    case, the card may not respond to this extra abort command and ESDHC will
    get Response Timeout.  It is recommended to manually send an abort command
    with RSPTYP[1:0] both bits cleared.
    
    Signed-off-by: default avatarJason Liu <jason.hui@linaro.org>
    4571de33
    History
    fsl_esdhc: Fix multi-block read restriction on i.MX53 eSDHCv2
    Jason Liu authored
    
    For freescale i.MX53 eSDHCv2, when using CMD12, cmdtype need
    to be set to ABORT, otherwise, next read command will hang.
    
    This is a software Software Restrictions in i.MX53 reference manual:
    
    29.7.8 Multi-block Read
    For pre-defined multi-block read operation, that is,the number of blocks
    to read has been defined by previous CMD23 for MMC, or pre-defined number
    of blocks in CMD53 for SDIO/SDCombo,or whatever multi-block read without
    abort command at card side, an abort command, either automatic or manual
    CMD12/CMD52, is still required by ESDHC after the pre-defined number of
    blocks are done, to drive the internal state machine to idle mode. In this
    case, the card may not respond to this extra abort command and ESDHC will
    get Response Timeout.  It is recommended to manually send an abort command
    with RSPTYP[1:0] both bits cleared.
    
    Signed-off-by: default avatarJason Liu <jason.hui@linaro.org>