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
  • host
  • omap_hsmmc.c
Find file BlameHistoryPermalink
  • Balaji T K's avatar
    mmc: omap_hsmmc: fix module re-insertion · fc307df8
    Balaji T K authored Apr 02, 2012
    
    
    OMAP4 and OMAP3 HSMMC IP registers differ by 0x100 offset.
    Adding the offset to platform_device resource structure
    increments the start address for every insmod operation.
    MMC command fails on re-insertion as module due to incorrect register
    base.  Fix this by updating the ioremap base address only.
    
    Signed-off-by: default avatarBalaji T K <balajitk@ti.com>
    Signed-off-by: default avatarVenkatraman S <svenkatr@ti.com>
    Signed-off-by: default avatarChris Ball <cjb@laptop.org>
    fc307df8