linux.git/drivers/video, branch v2.6.33

efifb: fix framebuffer handoff

2010-02-23T03:50:34+00:00

Commit 4410f3910947dcea8672280b3adecd53cec4e85e ("fbdev: add support for
handoff from firmware to hw framebuffers") didn't add fb_destroy
operation to efifb.  Fix it and change aperture_size to match size
passed to request_mem_region.

Addresses http://bugzilla.kernel.org/show_bug.cgi?id=15151

Signed-off-by: Marcin Slusarz 
Reported-by: Alex Zhavnerchik 
Tested-by: Alex Zhavnerchik 
Acked-by: Peter Jones 
Cc: Huang Ying 
Cc: Dave Airlie 
Cc: "Rafael J. Wysocki" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

imxfb: correct location of callbacks in suspend and resume

2010-02-03T02:11:22+00:00

The probe function passes a pointer to a struct fb_info to
platform_set_drvdata(), so don't interpret the return value of
platform_get_drvdata() as a pointer to struct imxfb_info.

The original imxfb_info *fbi backlight_power was NULL but in imxfb_suspend
it was 4 resulting in an oops as imxfb_suspend calls
imxfb_disable_controller(fbi) which in turn has

	if (fbi->backlight_power)
			fbi->backlight_power(0);

Signed-off-by: Uwe Kleine-König  
Acked-by: Sascha Hauer 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mx3fb: some debug and initialisation fixes

2010-02-03T02:11:21+00:00

Fix the kernel oops when dev_dbg is called with mx3_fbi->txd == NULL

Fix the late initialisation of mx3fb->backlight_level.  If not, in the
chain of function started by init_fb_chan(), in __blank() call
sdc_set_brightness(mx3fb, mx3fb->backlight_level) that will shut down the
CONTRAST PWM output.

Signed-off-by: Alberto Panizzo 
Acked-by: Guennadi Liakhovetski  gmx.de>
Cc: Sascha Hauer 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

revert "drivers/video/s3c-fb.c: fix clock setting for Samsung SoC Framebuffer"

2010-01-16T20:15:40+00:00

Fix divide by zero and broken output.  Commit 600ce1a0fa ("fix clock
setting for Samsung SoC Framebuffer") introduced a mandatory refresh
parameter to the platform data for the S3C framebuffer but did not
introduce any validation code, causing existing platforms (none of which
have refresh set) to divide by zero whenever the framebuffer is
configured, generating warnings and unusable output.

Ben Dooks noted several problems with the patch:

 - The platform data supplies the pixclk directly and should already
   have taken care of the refresh rate.
 - The addition of a window ID parameter doesn't help since only the
   root framebuffer can control the pixclk.
 - pixclk is specified in picoseconds (rather than Hz) as the patch
   assumed.

and suggests reverting the commit so do that.  Without fixing this no
mainline user of the driver will produce output.

[akpm@linux-foundation.org: don't revert the correct bit]
Signed-off-by: Mark Brown 
Cc: InKi Dae 
Cc: Kyungmin Park 
Cc: Krzysztof Helt 
Cc: Marek Szyprowski 
Cc: Ben Dooks 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

viafb: fix acceleration for some chips

2010-01-16T20:15:37+00:00

Fix a regression in hardware acceleration which made the accelerated
framebuffer unusable on some chips.  These need extra initialization and
an extra flag which is no longer needed/available on current chips.

Signed-off-by: Erik-Jan Post 
Signed-off-by: Florian Tobias Schandinat 
Cc: Scott Fang 
Cc: Joseph Chan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

viafb: do modesetting after updating variables

2010-01-16T20:15:37+00:00

Reorder viafb_set_par to allow using the updated variables in
viafb_setmode.  This fixes a regression that prevented proper runtime mode
changes.

Signed-off-by: Erik-Jan Post 
Signed-off-by: Florian Tobias Schandinat 
Cc: Scott Fang 
Cc: Joseph Chan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

viafb: fix LCD hardware cursor regression

2010-01-16T20:15:37+00:00

Although I'd consider this a hardware bug, as there is hardware out that
for whatever reason does not support hardware cursors on LCD output we
have to care about it in the driver.  This fixes a regression (invisible
cursor) introduced by:

    viafb: cleanup viafb_cursor

Signed-off-by: Florian Tobias Schandinat 
Reported-by: Julian Wollrath 
Tested-by: Julian Wollrath 
Cc: Scott Fang 
Cc: Joseph Chan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'for-linus' of git://gitorious.org/linux-omap-dss2/linux

2010-01-13T05:04:04+00:00

* 'for-linus' of git://gitorious.org/linux-omap-dss2/linux:
  OMAP: DSS2: OMAPFB: fix crash when panel driver was not loaded
  OMAP: DSS2: Reject scaling settings when they cannot be supported
  OMAP: DSS2: Make check-delay-loops consistent
  OMAP: DSS2: OMAPFB: fix omapfb_free_fbmem()
  video/omap: add __init/__exit macros to drivers/video/omap/lcd_htcherald.c
  OMAP: DSS2: Fix compile warning
  MAINTAINERS: Combine DSS2 and OMAPFB2 into one entry
  MAINTAINERS: change omapfb maintainer
  OMAP: OMAPFB: add dummy release function for omapdss
  OMAP: OMAPFB: fix clk_get for RFBI
  OMAP: DSS2: RFBI: convert to new kfifo API
  OMAP: DSS2: Fix crash when panel doesn't define enable_te()
  OMAP: DSS2: Collect interrupt statistics
  OMAP: DSS2: DSI: print debug DCS cmd in hex
  OMAP: DSS2: DSI: fix VC channels in send_short and send_null

OMAP: DSS2: OMAPFB: fix crash when panel driver was not loaded

2010-01-12T10:10:55+00:00

If the panel's probe had failed, omapfb would still go on, eventually
crashing.

A better fix would be to handle each display properly, and leaving just
the failed display out. But that is a bigger change.

Signed-off-by: Tomi Valkeinen

OMAP: DSS2: Reject scaling settings when they cannot be supported

2010-01-12T10:10:19+00:00

If the scaling ratio is below 0.5 video output width can't be identical
to the display width. Reject such settings.

Signed-off-by: Ville Syrjälä 
Acked-by: Tomi Valkeinen