linux-toradex.git/drivers/video/pxafb.h, branch v3.2.47

ARM: pxafb: rework pxafb overlay memory management

2011-03-16T09:37:03+00:00

PXAFB overlay memory management is something messy:
- it allocates memory dynamically on open/release, and it results
  in memory allocation failure after ~1h of uptime (system does not have
  115k of physically contiguous memory)
- in release callback it tries to free memory even if it was not
  allocated.

Also driver touches FDADR1 on main plane reconfiguration, and it can cause
problems if overlay1 is enabled.

This patch attempts to fix those issues.

Patch is based on Russell King's work.

Signed-off-by: Vasily Khoruzhick 
Signed-off-by: Eric Miao

[ARM] pxafb: add support for overlay1 and overlay2 as framebuffer devices

2008-12-29T10:00:04+00:00

PXA27x and later processors support overlay1 and overlay2 on-top of the
base framebuffer (although under-neath the base is also possible). They
support palette and no-palette RGB formats, as well as YUV formats (only
available on overlay2). These overlays have dedicated DMA channels and
behave in a similar way as a framebuffer.

This heavily simplified and re-structured work is based on the original
pxafb_overlay.c (which is pending for mainline merge for a long time).

The major problems with this pxafb_overlay.c are (if you are interested
in the history):

  1. heavily redundant (the control logics for overlay1 and overlay2 are
     actually identical except for some small operations,  which are now
     abstracted into a 'pxafb_layer_ops' structure)

  2. a lot of useless and un-tested code (two workarounds which are now
     fixed on mature silicons)

  3. cursorfb is actually useless, hardware cursor should not be used
     this way, and the code was actually un-tested for a long time.

The code in this patch should be self-explanatory, I tried to add minimum
comments. As said, this is basically simplified, there are several things
still on the pending list:

  1. palette mode is un-supported and un-tested (although re-using the
     palette code of the base framebuffer is actually very easy now with
     previous clean-up patches)

  2. fb_pan_display for overlay(s) is un-supported

  3. the base framebuffer can actually be abstracted by 'pxafb_layer' as
     well, which will help further re-use of the code and keep a better
     and consistent structure. (This is the reason I named it 'pxafb_layer'
     instead of 'pxafb_overlay' or something alike)

See Documentation/fb/pxafb.txt for additional usage information.

Signed-off-by: Eric Miao 
Cc: Rodolfo Giometti 
Signed-off-by: Eric Miao

[ARM] pxafb: cleanup of the timing checking code

2008-12-29T09:59:17+00:00

Signed-off-by: Eric Miao 
Signed-off-by: Eric Miao

[ARM] pxafb: add support for FBIOPAN_DISPLAY by dma braching

2008-12-29T09:59:17+00:00

dma branching is enabled by extending the current setup_frame_dma()
function to allow a 2nd set of frame/palette dma descriptors to be
used.

As a result, pxafb_dma_buff.dma_desc[], pxafb_dma_buff.pal_desc[]
and pxafb_info.fdadr[] are doubled.

This allows maximum re-use of the current dma setup code, although
the pxafb_info.fdadr[xx] for FBRx register values looks a bit odd.

Signed-off-by: Eric Miao 
Signed-off-by: Eric Miao

[ARM] pxafb: allow video memory size to be configurable

2008-12-29T09:59:16+00:00

The amount of video memory size is decided according to the following
order:

1.  x  x  by default, which is the backward
   compatible way

2. size specified in platform data

3. size specified in module parameter 'options' string or specified in
   kernel boot command line (see updated Documentation/fb/pxafb.txt)

And now since the memory is allocated from system memory, the pxafb_mmap
can be removed and the default fb_mmap() should be working all right.

Also, since we now have introduced the 'struct pxafb_dma_buff' for DMA
descriptors and palettes, the allocation can be separated cleanly.

NOTE: the LCD DMA actually supports chained transfer (i.e. page-based
transfers), to simplify the logic and keep the performance (with less
TLB misses when accessing from memory mapped user space), the memory
is allocated by alloc_pages_*() to ensures it's physical contiguous.

Signed-off-by: Eric Miao 
Signed-off-by: Eric Miao

[ARM] pxafb: make {backlight,lcd}_power() members of struct pxafb_info

2008-12-02T06:43:47+00:00

instead of holding them as static pointers.

Signed-off-by: Daniel Mack 
Signed-off-by: Eric Miao

pxafb: convert ctrlr_sem in a mutex

2008-07-24T17:47:37+00:00

The semaphore ctrlr_sem is used as a mutex.  Convert it to the mutex API.

Signed-off-by: Matthias Kaehlcke 
Cc: Daniel Mack 
Cc: Eric Miao 
Cc: Russell King 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

pxafb: preliminary smart panel interface support

2008-04-30T15:29:32+00:00

Signed-off-by: Daniel Mack 
Signed-off-by: Eric Miao 
Cc: "Antonino A. Daplas" 
Cc: Russell King 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

pxafb: move parallel LCD timing setup into dedicate function

2008-04-30T15:29:32+00:00

the new_regs stuff has been removed, and all the setup (modification to those
fbi->reg_*) is protected with IRQ disabled

   * disable IRQ is too heavy here, provided that no IRQ context will
     touch the fbi->reg_* and the only possible contending place is
     in the CPUFREQ_POSTCHANGE (task context), a mutex will be better,
     leave this for future improvement

Signed-off-by: eric miao 
Cc: "Antonino A. Daplas" 
Cc: Russell King 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

pxafb: use completion for LCD disable wait code

2008-04-30T15:29:32+00:00

Signed-off-by: eric miao 
Cc: "Antonino A. Daplas" 
Cc: Russell King 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds