[PATCH v4 1/8] DSS2: OMAPFB: Refactor overlay address calculations

From: Ville Syrjälä ville.syrj...@nokia.com Split the overlay address calculations into their own function. Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- drivers/video/omap2/omapfb/omapfb-main.c | 63 ++ 1 files changed, 38 insertions(+), 25 deletions(-)

[PATCH v4 3/8] DSS2: OMAPFB: Skip unnecessary set_overlay_info()

From: Ville Syrjälä ville.syrj...@nokia.com In omapfb_enable_overlay() if the overlay state is already what we want skip the set_overlay_info(). Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- drivers/video/omap2/omapfb/omapfb.h |2 ++ 1 files changed, 2 insertions(+), 0

omapfb mem_idx patchset

This patchset is based on the v3 monolithic patch. These are the changes from v3: * split up into smaller chunks * OMAPFB_MEM_IDX defines fixed to use the full byte * unnecessary changes removed * converted to use rwsems * further modified further to make lockdep happy * some debug WARN_ON()s

[PATCH v4 2/8] DSS2: OMAPFB: Check var even if there isn't memory

From: Ville Syrjälä ville.syrj...@nokia.com If video memory hasn't been allocate have check_fb_var() still check most of the settings, just skip the ones involving the size of the memory region. Also skip the memory address calculations in omapfb_setup_overlay() if there's no memory.

[PATCH v4 5/8] DSS2: OMAPFB: Add locking for memory regions

From: Ville Syrjälä ville.syrj...@nokia.com 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ä ville.syrj...@nokia.com ---

[PATCH v4 4/8] DSS2: OMAPFB: Add support for switching memory regions

From: Ville Syrjälä ville.syrj...@nokia.com 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

[PATCH v4 7/8] DSS2: OMAPFB: Make lockdep happy

From: Ville Syrjälä ville.syrj...@nokia.com 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

[PATCH v4 6/8] DSS2: OMAPFB: Convert the memory region locking to rwsem

From: Ville Syrjälä ville.syrj...@nokia.com R/W semaphore is a goof fit for the memory region locking pattern. So use it. Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- drivers/video/omap2/omapfb/omapfb-ioctl.c | 10 ++ drivers/video/omap2/omapfb/omapfb-main.c |2 +-

[PATCH v4 8/8] DSS2: OMAPFB: Add some locking debug checks

From: Ville Syrjälä ville.syrj...@nokia.com 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ä ville.syrj...@nokia.com --- drivers/video/omap2/omapfb/omapfb-ioctl.c |2 ++

[PATCH 2/4] DSS2: Check if display supports update mode changes

From: Ville Syrjälä ville.syrj...@nokia.com Check whether the display actually has the set_update_mode() function before calling it. Only the sysfs codepath was broken, the omapfb ioctl had the necessary protection. Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com ---

[PATCH v3 1/4] DSS2: OMAPFB: Add support for switching memory regions

From: Ville Syrjälä ville.syrj...@nokia.com 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

[PATCH 4/4] DSS2: clear spurious SYNC_LOST_DIGIT interrupts

From: Ville Syrjälä ville.syrj...@nokia.com When DSS transitions from off mode to on VENC may generate a spurious SYNC_LOST_DIGIT error. Just ack it when restoring the context. Also restore IRQENABLE last to avoid triggering interrupts before the context is fully restored. Signed-off-by: Ville

[PATCH 3/4] DSS2: Make wait_for_go() succeed for disabled displays

From: Ville Syrjälä ville.syrj...@nokia.com When the display is not active make the wait_for_go() functions return immediately. Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- drivers/video/omap2/dss/manager.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git

[PATCH v2] DSS2: OMAPFB: Add support for switching memory regions

From: Ville Syrjälä ville.syrj...@nokia.com 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 source_idx parameter of omapfb_plane_info. If the source_idx is specified it will be

[PATCH 1/3] OMAPFB: install omapfb.h

From: Ville Syrjälä ville.syrj...@nokia.com omapfb has several custom ioctls so user space needs the header in order to utilize them. Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- include/linux/Kbuild |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

[PATCH 2/3] DSS2: OMAPFB: Constify some function parameters

From: Ville Syrjälä ville.syrj...@nokia.com Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com --- drivers/video/omap2/omapfb/omapfb-main.c | 18 +- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/video/omap2/omapfb/omapfb-main.c

[PATCH 3/3] DSS2: OMAPFB: Add support for switching memory regions

From: Ville Syrjälä ville.syrj...@nokia.com 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 source_idx parameter of omapfb_plane_info. If the source_idx is specified it will be