From: Mayuresh Janorkar <mayur@ti.com>
To: tomi.valkeinen@nokia.com
Cc: linux-omap@vger.kernel.org, Gustavo Diaz Prado <x0083741@ti.com>,
Mayuresh Janorkar <mayur@ti.com>
Subject: [PATCH] omap4: fb: Adds missing display update call when panning
Date: Thu, 15 Jul 2010 18:07:02 +0530 [thread overview]
Message-ID: <1279197422-23662-1-git-send-email-mayur@ti.com> (raw)
From: Gustavo Diaz Prado <x0083741@ti.com>
Adds the missing display update call when panning, this
is needed for the DSI panel when the auto-update feature is
not enabled.
Signed-off-by: Gustavo Diaz Prado <x0083741@ti.com>
Signed-off-by: Mayuresh Janorkar <mayur@ti.com>
---
drivers/video/omap2/omapfb/omapfb-main.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/drivers/video/omap2/omapfb/omapfb-main.c b/drivers/video/omap2/omapfb/omapfb-main.c
index 4abb1d1..12d5382 100644
--- a/drivers/video/omap2/omapfb/omapfb-main.c
+++ b/drivers/video/omap2/omapfb/omapfb-main.c
@@ -1068,7 +1068,8 @@ static int omapfb_pan_display(struct fb_var_screeninfo *var,
{
struct omapfb_info *ofbi = FB2OFB(fbi);
struct fb_var_screeninfo new_var;
- int r;
+ int r = 0;
+ struct omap_dss_device *display = fb2display(fbi);
DBG("pan_display(%d)\n", FB2OFB(fbi)->id);
@@ -1086,6 +1087,11 @@ static int omapfb_pan_display(struct fb_var_screeninfo *var,
r = omapfb_apply_changes(fbi, 0);
+ if (display && display->driver->update &&
+ display->driver->get_update_mode(display)
+ == OMAP_DSS_UPDATE_MANUAL)
+ display->driver->update(display, 0, 0, var->xres, var->yres);
+
omapfb_put_mem_region(ofbi->region);
return r;
--
1.5.4.7
next reply other threads:[~2010-07-15 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 12:37 Mayuresh Janorkar [this message]
2010-07-15 12:48 ` [PATCH] omap4: fb: Adds missing display update call when panning Shilimkar, Santosh
2010-07-21 13:19 ` Janorkar, Mayuresh
2010-07-26 7:47 ` Tomi Valkeinen
2010-08-11 10:14 ` Janorkar, Mayuresh
2010-08-16 13:40 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1279197422-23662-1-git-send-email-mayur@ti.com \
--to=mayur@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=x0083741@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).