Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • linux-vf linux-vf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-vflinux-vf
  • Repository
Switch branch/tag
  • linux-vf
  • drivers
  • mmc
  • core
  • core.c
Find file BlameHistoryPermalink
  • Paul Walmsley's avatar
    mmc: use really long write timeout to deal with crappy cards · 3bdc9ba8
    Paul Walmsley authored Mar 12, 2012
    Several people have noticed that crappy SD cards take much longer to
    complete multiple block writes than the 300ms that Linux specifies.
    Try to work around this by using a three second write timeout instead.
    
    This is a generalized version of a patch from Chase Maupin
    <Chase.Maupin@ti.com>, whose patch description said:
    
    * With certain SD cards timeouts like the following have been seen
      due to an improper calculation of the dto value:
        mmcblk0: error -110 transferring data, sector 4126233, nr 8,
        card status 0xc00
    * By removing the dto calculation and setting the timeout value
      to the maximum specified by the SD card specification part A2
      section 2.2.15 these timeouts can be avoided.
    * This change has been used by beagleboard users as well as the
      Texas Instruments SDK without a negative impact.
    * There are multiple discussion threads about this but the most
      relevant ones are:
        * http://talk.maemo.org/showthread.php?p=1000707#post1000707
        * http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42213.html
    
    
    * Original proposal for this fix was done by Sukumar Ghoral of
      Texas Instruments
    * Tested using a Texas Instruments AM335x EVM
    
    Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
    Tested-by: default avatarTony Lindgren <tony@atomide.com>
    Signed-off-by: default avatarChris Ball <cjb@laptop.org>
    3bdc9ba8