linux-toradex.git/drivers/video, branch v4.2.8

fbcon: initialize blink interval before calling fb_set_par

2015-11-09T22:37:36+00:00

commit f235f664a8afabccf863a5dee4777d2d7b676fda upstream.

Since commit 27a4c827c34ac4256a190cc9d24607f953c1c459
    fbcon: use the cursor blink interval provided by vt

a PPC64LE kernel fails to boot when fbcon_add_cursor_timer uses an
uninitialized ops->cur_blink_jiffies. Prevent by initializing
in fbcon_init before the call to info->fbops->fb_set_par.

Reported-and-tested-by: Alistair Popple 
Signed-off-by: Scot Doyle 
Signed-off-by: Greg Kroah-Hartman

fbcon: unconditionally initialize cursor blink interval

2015-08-10T14:20:32+00:00

A sun7i-a20-olinuxino-micro fails to boot when kernel parameter
vt.global_cursor_default=0. The value is copied to vc->vc_deccm
causing the initialization of ops->cur_blink_jiffies to be skipped.
Unconditionally initialize it.

Reported-and-tested-by: Jonathan Liu 
Signed-off-by: Scot Doyle 
Acked-by: Pavel Machek 
Signed-off-by: Tomi Valkeinen

video: Fix possible leak in of_get_videomode()

2015-08-10T12:11:12+00:00

In case videomode_from_timings() fails in function of_get_videomode(), the
allocated display timing data is not freed in the exit path. Make sure that
display_timings_release() is called in any case. Detected by Coverity CID
1309681.

Signed-off-by: Christian Engelmayer 
Signed-off-by: Tomi Valkeinen

video: fbdev: pxa3xx_gcu: prepare the clocks

2015-08-10T09:25:43+00:00

The clocks need to be prepared before being enabled. Without it a
warning appears in the drivers probe path :

WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:707 clk_core_enable+0x84/0xa0()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 4.2.0-rc3-cm-x300+ #804
Hardware name: CM-X300 module
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (warn_slowpath_common+0x7c/0xb4)
[] (warn_slowpath_common) from [] (warn_slowpath_null+0x1c/0x24)
[] (warn_slowpath_null) from [] (clk_core_enable+0x84/0xa0)
[] (clk_core_enable) from [] (clk_enable+0x20/0x34)
[] (clk_enable) from [] (pxa3xx_gcu_probe+0x148/0x338)
[] (pxa3xx_gcu_probe) from
[] (platform_drv_probe+0x30/0x94)

Signed-off-by: Robert Jarzmik 
Signed-off-by: Tomi Valkeinen

OMAPDSS: Fix omap_dss_find_output_by_port_node() port refcount decrement

2015-08-10T09:22:40+00:00

Fix omap_dss_find_output_by_port_node() port parameter refcount
decrementation. The only user of dss_of_port_get_parent_device()
function is omap_dss_find_output_by_port_node() and it assumes the
refcount of the port parameter is not decremented by the call.

Signed-off-by: Jyri Sarha 
Signed-off-by: Tomi Valkeinen

OMAPDSS: Fix node refcount leak in omapdss_of_get_next_port()

2015-08-10T09:22:35+00:00

Fix node refcount leak in omapdss_of_get_next_port().

Signed-off-by: Jyri Sarha 
Signed-off-by: Tomi Valkeinen

fbdev: select versatile helpers for the integrator

2015-08-10T09:20:38+00:00

Commit 11c32d7b6274cb0f554943d65bd4a126c4a86dcd
"video: move Versatile CLCD helpers" missed the fact
that the Integrator/CP is also using the helper, and
as a result the platform got only stubs and no graphics.
Add this as a default selection to Kconfig so we have
graphics again.

Fixes: 11c32d7b6274 (video: move Versatile CLCD helpers)
Signed-off-by: Linus Walleij 
Signed-off-by: Tomi Valkeinen

stifb: Implement hardware accelerated copyarea

2015-07-10T19:44:19+00:00

This patch adds hardware assisted scrolling. The code is based upon the
following investigation: https://parisc.wiki.kernel.org/index.php/NGLE#Blitter

A simple 'time ls -la /usr/bin' test shows 1.6x speed increase over soft
copy and 2.3x increase over FBINFO_READS_FAST (prefer soft copy over
screen redraw) on Artist framebuffer.

Signed-off-by: Alex Ivanov 
Signed-off-by: Helge Deller

Merge tag 'fbdev-fixes-4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux

2015-07-03T19:11:17+00:00

Pull fbdev fix from Tomi Valkeinen:
 "Fix display regression on TI AM4xxx boards"

* tag 'fbdev-fixes-4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux:
  OMAPDSS: fix probing if rfbi device is enabled

OMAPDSS: fix probing if rfbi device is enabled

2015-07-02T12:20:10+00:00

After the commit 736e60ddc215b85e73bbf7da26e1cde84cc9500f ("OMAPDSS:
componentize omapdss") the dss core device will wait until all the
subdevices have been successfully probed. However, we don't have a
working driver for RFBI, so if RFBI device exists, omapdss will never
get probed.

All the .dtsi files set RFBI as disabled, except am4372.dtsi. This
causes omapdss probe to not finish on AM4 devices.

This patch makes omapdss driver skip adding rfbi device as a
subcomponent, solving the issue.

This should be reverted when we have a working RFBI driver.

Signed-off-by: Tomi Valkeinen 
Reported-by: Felipe Balbi