kernel/drivers/video/fbdev/omap2/omapfb, branch linux-4.3.y

mm: mark most vm_operations_struct const

2015-09-10T20:29:01Z

With two exceptions (drm/qxl and drm/radeon) all vm_operations_struct structs should be constant. Signed-off-by: Kirill A. Shutemov Reviewed-by: Oleg Nesterov Cc: "H. Peter Anvin" Cc: Andy Lutomirski Cc: Dave Hansen Cc: Ingo Molnar Cc: Minchan Kim Cc: Thomas Gleixner Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

OMAPDSS: DISPC: remove OMAPDSS_DRIVE_SIG_OPPOSITE_EDGES

2015-02-26T10:15:11Z

DISPC can drive data lines either on rising or falling pixel clock edge, which can be configured by the user. Sync lines can also be driven on rising or falling pixel clock edge, but additionally the HW can be configured to drive the sync lines on opposite clock edge from the data lines. This opposite edge setting does not make any sense, as the same effect can be achieved by just setting the sync lines to be driven on the other edge compared to the data lines. It feels like some kind of backward compatibility option, even if all DSS versions seem to have the same implementation. To simplify the code and configuration of the signals, and to make the dispc timings more compatible with what is used on other platforms, let's just remove the whole opposite-edge support. The drivers that used OMAPDSS_DRIVE_SIG_OPPOSITE_EDGES setting are changed so that they use the opposite setting from the data edge. Signed-off-by: Tomi Valkeinen

omapfb: Return error code when applying overlay settings fails

2015-02-04T10:41:53Z

the check of the return code is missing, user space does not get notified about the error condition: omapdss OVERLAY error: overlay 2 horizontally not inside the display area (403 + 800 >= 800) omapdss APPLY error: failed to apply settings: illegal configuration. Signed-off-by: Peter Meerwald Signed-off-by: Tomi Valkeinen

Merge branch 'platform/remove_owner' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux into driver-core-next

2014-11-04T03:53:56Z

Remove all .owner fields from platform drivers

OMAPFB: fix releasing overlays

2014-10-22T08:07:08Z

omapfb disables all the overlays when freeing resources, but it should also remove those overlays from overlay managers. Not doing so causes a crash if omapfb is unbound and bound, or omapfb module is removed and loaded, while keeping omapdss around. Fix this by calling unset_manager() for all overlays. Signed-off-by: Tomi Valkeinen

OMAPFB: fix overlay disable when freeing resources.

2014-10-22T08:07:08Z

When omapfb is shutting down, it will disable all the overlays. However, instead of actually disabling all the overlays, it disables only all the overlays that are currently attached to framebuffers. On OMAP4+, this leaves the fourth overlay left enabled. Fix the loop so that we actually go through all the overlays. Signed-off-by: Tomi Valkeinen

OMAPFB: remove __exit annotation

2014-10-22T08:07:07Z

If we leave __exit annotation, driver can't be unbound through sysfs. Signed-off-by: Felipe Balbi Signed-off-by: Tomi Valkeinen

OMAPFB: add missing MODULE_ALIAS()

2014-10-22T08:06:56Z

without MODULE_ALIAS(), omapfb won't get loaded automatically. Signed-off-by: Felipe Balbi Signed-off-by: Tomi Valkeinen

video: fbdev: omap2: omapfb: drop owner assignment from platform_drivers

2014-10-20T14:21:55Z

A platform_driver does not need to set an owner, it will be populated by the driver core. Signed-off-by: Wolfram Sang

arm, fbdev, omap2, LLVMLinux: Remove nested function from omapfb

2014-09-30T10:11:53Z

Replace the use of nested functions where a normal function will suffice. Nested functions are not liked by upstream kernel developers in general. Their use breaks the use of clang as a compiler, and doesn't make the code any better. This code now works for both gcc and clang. Signed-off-by: Behan Webster Suggested-by: Arnd Bergmann Cc: Arnd Bergmann Reviewed-by: Felipe Balbi Signed-off-by: Tomi Valkeinen