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
  • arch
  • arm64
  • include
  • asm
  • cache.h
Find file BlameHistoryPermalink
  • Will Deacon's avatar
    Revert "arm64: Revert L1_CACHE_SHIFT back to 6 (64-byte cache line size)" · 3f251cf0
    Will Deacon authored Mar 27, 2018
    This reverts commit 1f85b42a
    
    .
    
    The internal dma-direct.h API has changed in -next, which collides with
    us trying to use it to manage non-coherent DMA devices on systems with
    unreasonably large cache writeback granules.
    
    This isn't at all trivial to resolve, so revert our changes for now and
    we can revisit this after the merge window. Effectively, this just
    restores our behaviour back to that of 4.16.
    
    Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
    3f251cf0