public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: Suspend/Resume support with Omap2fb
Date: Fri, 13 Mar 2009 11:26:09 +0200	[thread overview]
Message-ID: <1236936369.457.7.camel@tubuntu> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940427C52071@dbde02.ent.ti.com>

On Fri, 2009-03-13 at 10:17 +0100, ext Hiremath, Vaibhav wrote:

> > > > Hi,
> > > >
> > > > On Thu, 2009-03-12 at 19:26 +0100, ext Hiremath, Vaibhav wrote:
> > > > > Hi,
> > > > >
> > > > > Finally I could able to find the root-cause, actually some of
> > the
> > > > previous observations miss-led me to dig into power management,
> > > > suspend/resume path and clock structure. But after bit debugging
> > and
> > > > with the help of Sanjeev, we got the rid of it.
> > > > >
> > > > > The issue is with DSS2 library, inside function
> > > > "dpi_display_suspend". It calls dispc_enable_lcd_out(0), but
> > doesn't
> > > > wait till the frame-done interrupt. And due to this I was
> > getting
> > > > some abrupt behavior in suspend/resume path.
> > > > > Actually in the beginning I overlooked legacy frame-buffer
> > driver,
> > > > which handles this scenario perfectly.
> > > >
> > > > dispc_enable_lcd_out(0) waits for FRAMEDONE. Please use the
> > latest
> > > > DSS2
> > > > version from my git repository =).
> > > >
> > > [Hiremath, Vaibhav] Ohhh great, but I think yesterday only I
> > pulled changes from your repository, and it was not there.
> > >
> > > Ok, but it's great that you merged the change.
> > 
> > No, it's been there for quite a while... (weeks, months, I don't
> > remember).
> > 
> [Hiremath, Vaibhav] May be I looked into wrong branch, can you please provide in which branch of yours the change is? So that I can validate my changes and make it more close to yours, it will be easy for me to migrate in the future.

All the latest DSS2 stuff is in the master branch.

 Tomi



  reply	other threads:[~2009-03-13  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 18:26 Suspend/Resume support with Omap2fb Hiremath, Vaibhav
2009-03-13  8:30 ` Tomi Valkeinen
2009-03-13  9:10   ` Hiremath, Vaibhav
2009-03-13  9:13     ` Tomi Valkeinen
2009-03-13  9:17       ` Hiremath, Vaibhav
2009-03-13  9:26         ` Tomi Valkeinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-11  6:55 Hiremath, Vaibhav
2009-03-11  7:53 ` Tomi Valkeinen
2009-03-11  8:46   ` Hiremath, Vaibhav
2009-03-11  9:31     ` Tomi Valkeinen
2009-03-11 10:47       ` Hiremath, Vaibhav
2009-03-11 12:49         ` Tomi Valkeinen
2009-03-11 18:08           ` Hiremath, Vaibhav

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=1236936369.457.7.camel@tubuntu \
    --to=tomi.valkeinen@nokia.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /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