Re: DSS2/PM on 3.2 broken?

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

On Thu, 2012-01-12 at 11:28 +0200, Tomi Valkeinen wrote:
> Hi,
> 
> On Wed, 2012-01-11 at 15:15 +0000, Joe Woodward wrote:
> 
> > > The pm_runtime_get_sync() call in dss_runtime_get() is returning  a 
> > > negative value, could you print out that value too?
> > > 
> > > If the call to pm_runtime_get_sync() fails, we bail out immediately. So
> > > the LCD interface shouldn't have been enabled at all. I don't know why 
> > > we get sync lost errors.
> > > 
> > > There is a possibility that the LCD interface wasn't switched off when 
> > > for some reason when we suspended, and switching on the clocks again 
> > > tries to start the transfer without DSS being configured correctly?
> 
> I can reproduce this on my Overo. The problem goes away if I change
> dss's and dispc'c pm_runtime_put() calls to pm_runtime_put_sync(). But
> I'm not quite sure why.

(I seem to have not waken up today...)

I also forgot to mention that the fail happens in
drivers/base/power/runtime.c:rpm_resume(), where the check
"dev->power.disable_depth > 0" causes the function to return EACCES.

I'm not sure what disable_depth > 0 means.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]