Linux Kernel  3.7.1
 All Data Structures Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Data Fields
omap_gem_object Struct Reference

Data Fields

struct drm_gem_object base
 
struct list_head mm_list
 
uint32_t flags
 
uint16_t width
 
uint16_t height
 
uint32_t roll
 
dma_addr_t paddr
 
uint32_t paddr_cnt
 
struct tiler_blockblock
 
struct page ** pages
 
dma_addr_taddrs
 
voidvaddr
 
struct {
   uint32_t   write_pending
 
   uint32_t   write_complete
 
   uint32_t   read_pending
 
   uint32_t   read_complete
 
sync
 

Detailed Description

Definition at line 45 of file omap_gem.c.

Field Documentation

dma_addr_t* addrs

addresses corresponding to pages in above array

Definition at line 90 of file omap_gem.c.

struct drm_gem_object base

Definition at line 46 of file omap_gem.c.

tiler block used when buffer is remapped in DMM/TILER.

Definition at line 81 of file omap_gem.c.

uint32_t flags

Definition at line 50 of file omap_gem.c.

uint16_t height

Definition at line 53 of file omap_gem.c.

struct list_head mm_list

Definition at line 48 of file omap_gem.c.

dma_addr_t paddr

If buffer is allocated physically contiguous, the OMAP_BO_DMA flag is set and the paddr is valid. Also if the buffer is remapped in TILER and paddr_cnt > 0, then paddr is valid. But if you are using the physical address and OMAP_BO_DMA is not set, then you should be going thru omap_gem_{get,put}_paddr() to ensure the mapping is not removed from under your feet.

Note that OMAP_BO_SCANOUT is a hint from userspace that DMA capable buffer is requested, but doesn't mean that it is. Use the OMAP_BO_DMA flag to determine if the buffer has a DMA capable physical address.

Definition at line 71 of file omap_gem.c.

uint32_t paddr_cnt

of users of paddr

Definition at line 76 of file omap_gem.c.

struct page** pages

Array of backing pages, if allocated. Note that pages are never allocated for buffers originally allocated from contiguous memory

Definition at line 87 of file omap_gem.c.

uint32_t read_complete

Definition at line 117 of file omap_gem.c.

uint32_t read_pending

Definition at line 116 of file omap_gem.c.

uint32_t roll

roll applied when mapping to DMM

Definition at line 56 of file omap_gem.c.

struct { ... } * sync
void* vaddr

Virtual address, if mapped.

Definition at line 95 of file omap_gem.c.

uint16_t width

width/height for tiled formats (rounded up to slot boundaries)

Definition at line 53 of file omap_gem.c.

uint32_t write_complete

Definition at line 115 of file omap_gem.c.

uint32_t write_pending

Definition at line 114 of file omap_gem.c.


The documentation for this struct was generated from the following file: