Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • drivers
  • gpu
  • drm
  • radeon
  • radeon_display.c
Find file BlameHistoryPermalink
  • Jerome Glisse's avatar
    drm/radeon/kms: Do not unpin buffer in fb destruction · 6398d424
    Jerome Glisse authored Jan 13, 2010
    
    
    It's not necessary to unpin buffer in fb destruction. pin/unpin
    need to be balanced and we don't pin in fb creation. We pin when
    an fb is associated to a crtc and unpin when the fb is disassociated
    from the crtc.
    
    Note:
    Maybe we should take reference on fb in set_base callback so fb
    doesn't disappear until it's unbind from ctrc.
    
    Signed-off-by: default avatarJerome Glisse <jglisse@redhat.com>
    Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
    6398d424