1. 13 Nov, 2012 2 commits
    • Tomi Valkeinen's avatar
      OMAPFB: use dma_alloc_attrs to allocate memory · 0049fb26
      Tomi Valkeinen authored
      Use dma_alloc_attrs to allocate memory instead of omap specific vram
      allocator. After this we can remove the omap vram allocator.
      
      There are some downsides to this change:
      
      1) dma_alloc_attrs doesn't let us allocate at certain physical address.
      However, this should not be a problem as this feature of vram allocator
      is only used when reserving the framebuffer that was initialized by the
      bootloader, and we don't currently support "passing" a framebuffer from
      the bootloader to the kernel anyway.
      
      2) dma_alloc_attrs, as of now, always ioremaps the allocated area, and
      we don't need the ioremap when using VRFB. This patch uses
      DMA_ATTR_NO_KERNEL_MAPPING for the allocation, but the flag is currently
      not operational.
      
      3) OMAPFB_GET_VRAM_INFO ioctl cannot return real values anymore. I
      changed the ioctl to return 64M for all the values, which, I hope, the
      applications will interpret as "there's enough vram".
      
      4) "vram" kernel parameter to define how much ram to reserve for video
      use no longer works. The user needs to enable CMA and use "cma"
      parameter.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      0049fb26
    • Tomi Valkeinen's avatar
      OMAP: FB: use DMA_BIT_MASK() for fb's coherent_dma_mask · 3f5ba55e
      Tomi Valkeinen authored
      Use DMA_BIT_MASK() for fb's coherent_dma_mask for clarity.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      3f5ba55e
  2. 04 Nov, 2012 1 commit
  3. 03 Nov, 2012 15 commits
  4. 02 Nov, 2012 22 commits