aboutsummaryrefslogtreecommitdiff
path: root/drivers/video/omap2/omapfb/omapfb-ioctl.c
AgeCommit message (Collapse)AuthorFilesLines
2010-08-05OMAP: DSS2: OMAPFB: add support for FBIO_WAITFORVSYNCGrazvydas Ignotas1-0/+12
FBIO_WAITFORVSYNC is a stardard ioctl for waiting vsync, already used by some userspace, so add it as an alias for OMAPFB_WAITFORVSYNC. Signed-off-by: Grazvydas Ignotas <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-05OMAP: DSS2: OMAPFB: Check fb2display() return valueJani Nikula1-1/+1
Make sure NULL return value of fb2display() is not referenced. Found by Coverity. Signed-off-by: Jani Nikula <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-03OMAP: DSS2: OMAPFB: Add some locking debug checksVille Syrjälä1-0/+2
Trigger WARN_ON() messages from various places in the code in case the memory region is not currently locked. Signed-off-by: Ville Syrjälä <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-03OMAP: DSS2: OMAPFB: Make lockdep happyVille Syrjälä1-11/+34
When more than one memory region needs to be lockd at the same time use the memory region id to fix the order in which the locks are taken. Also one needs to use the _nested() versions of the locking primitives. The memory region id can serve as the lock class there as well. Signed-off-by: Ville Syrjälä <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-03OMAP: DSS2: OMAPFB: Convert the memory region locking to rwsemVille Syrjälä1-8/+2
R/W semaphore is a good fit for the memory region locking pattern. So use it. Signed-off-by: Ville Syrjälä <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-03OMAP: DSS2: OMAPFB: Add locking for memory regionsVille Syrjälä1-11/+33
Add locking to the memory regions to make sure the memory region size won't be changed while some other piece of code is performing some checks or setup based on that information. Signed-off-by: Ville Syrjälä <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-08-03OMAP: DSS2: OMAPFB: Add support for switching memory regionsVille Syrjälä1-23/+102
Separate the memory region from the framebuffer device a little bit. It's now possible to select the memory region used by the framebuffer device using the new mem_idx parameter of omapfb_plane_info. If the mem_idx is specified it will be interpreted as an index into the memory regions array, if it's not specified the framebuffer's index is used instead. So by default each framebuffer keeps using it's own memory region which preserves backwards compatibility. This allows cloning the same memory region to several overlays and yet each overlay can be controlled independently since they can be associated with separate framebuffer devices. Signed-off-by: Ville Syrjälä <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-05-18OMAP: DSS2: check lock_fb_info() return valueJani Nikula1-1/+2
Give up if lock_fb_info() fails, following the same convention as other lock_fb_info() users. Signed-off-by: Jani Nikula <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-05-18OMAP: DSS2: fix lock_fb_info() and omapfb_lock() locking orderJani Nikula1-2/+2
Framebuffer ioctl processing forces lock_fb_info() -> omapfb_lock() locking order. Follow that order to avoid possible circular locking dependency, detected by lockdep. Signed-off-by: Jani Nikula <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move update() and sync()Tomi Valkeinen1-5/+5
Move update() and sync() from omap_dss_device to omap_dss_driver. Also, update was hardcoded to use virtual channel 0. This patch adds a parameter that specifies the VC. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move set/get_update_mode()Tomi Valkeinen1-4/+9
Move set/get_update_mode() from omap_dss_device to omap_dss_driver. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move enable/get_te()Tomi Valkeinen1-2/+3
Move enable/get_te() from omap_dss_device to omap_dss_driver. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move get_resolution()Tomi Valkeinen1-2/+2
Move get_resolution() from omap_dss_device to omap_dss_driver. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move wait_vsync()Tomi Valkeinen1-1/+1
Move wait_vsync() from omap_dss_device to overlay manager. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move memory_read()Tomi Valkeinen1-2/+2
Move memory_read() from omap_dss_device to omap_dss_driver. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-24OMAP: DSS2: move run_test()Tomi Valkeinen1-4/+4
Move run_test() from omap_dss_device to omap_dss_driver. This is part of a larger patch-set, which moves the control from omapdss driver to the display driver. Signed-off-by: Tomi Valkeinen <[email protected]>
2010-02-15OMAP: DSS2: OMAPFB: implement OMAPFB_GET_DISPLAY_INFOTomi Valkeinen1-0/+24
Previously the only place to get the size of the display was from the DSS's sysfs interface, making, for example, configuring overlays and doing updates on manual displays more difficult. Signed-off-by: Tomi Valkeinen <[email protected]>
2009-12-09OMAP: DSS2: omapfb driverTomi Valkeinen1-0/+755
Signed-off-by: Tomi Valkeinen <[email protected]>
Powered by cgit, Gruvboxed by Blaster4385.