public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Joe Woodward <jw@terrafix.co.uk>,
	khilman@ti.com, Paul Walmsley <paul@pwsan.com>
Cc: Archit Taneja <a0393947@ti.com>, linux-omap@vger.kernel.org
Subject: Re: v3.4-rc4 DSS PM problem (Was: Re: Problems with 3.4-rc5)
Date: Fri, 04 May 2012 17:58:20 +0300	[thread overview]
Message-ID: <1336143500.2552.23.camel@deskari> (raw)
In-Reply-To: <1336143281.2552.21.camel@deskari>

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

On Fri, 2012-05-04 at 17:54 +0300, Tomi Valkeinen wrote:
> Hi Kevin, Paul,
> 
> On Fri, 2012-05-04 at 15:09 +0100, Joe Woodward wrote:
> 
> > > > Ok, I can replicate it now. It seems to be somehow PM related. I
> > > > normally have USB gadget stuff compiled into kernel so that I can
> > > boot
> > > > via nfsroot with usb. After disabling USB support from the kernel, I
> > > can
> > > > see synclosts.
> > > > 
> > > > I have no idea yet what could be causing this. I've also tried adding
> > > > the couple of DSS patches which are in queue for next merge window,
> > > that
> > > > force OPP100 when DSS is enabled. They don't seem to help.
> > > 
> > > Also, at least on my setup, the sync lost doesn't happen very quickly
> > > after starting the video output, but (I think) only when the system
> > > starts to idle. My init scripts generate keys for sshd and some other
> > > stuff, and no sync lost there, only just before the shell prompt do I
> > > get a sync lost.
> > > 
> > >  Tomi
> > > 
> > 
> > That sounds like the same as I'm seeing. It seems that the sync lost jumps 
> > around a bit, from almost immediately (when the graphics are enabled), to 
> > up to 3 or 4 seconds later (still just before the shell prompt).
> > 
> > I'm assuming that setting the FIFO low and high points fixes your sync losts 
> > as well (as in the first patch you sent)?
> > 
> > I've also noted that doing things in different orders can sometimes fix the 
> > sync lost (such as disabling or enabling DVI output), but this all seems a bit 
> > random.
> > 
> > I'm just glad someone else has been able to replicate the problem :p
> 
> Kevin, Paul, there seems to be a problem with DSS on v3.4-rc4 running on
> omap3, causing DSS losing sync. I didn't notice this earlier as I have
> USB gadget compiled into my kernel. Removing USB support from the kernel
> causes the problem to appear, which more or less hints at a PM related
> issue.

Sorry, not sync lost, but FIFO underflow. So DSS is unable to fetch
enough pixels to update the panel. And in this case the pixel clock is
very low (small panel), so it's nowhere near any limit.

 Tomi


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

  reply	other threads:[~2012-05-04 14:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 11:52 Problems with 3.4-rc5 Joe Woodward
2012-05-02 12:24 ` Archit Taneja
2012-05-02 12:46   ` Joe Woodward
2012-05-03  8:28     ` Tomi Valkeinen
2012-05-03  8:49       ` Joe Woodward
2012-05-03 10:02         ` Archit Taneja
2012-05-03 13:07         ` Tomi Valkeinen
2012-05-04  9:19           ` Joe Woodward
2012-05-04 13:50             ` Tomi Valkeinen
2012-05-04 14:01               ` Tomi Valkeinen
2012-05-04 14:09                 ` Joe Woodward
2012-05-04 14:54                   ` v3.4-rc4 DSS PM problem (Was: Re: Problems with 3.4-rc5) Tomi Valkeinen
2012-05-04 14:58                     ` Tomi Valkeinen [this message]
2012-05-08 13:26                       ` Tomi Valkeinen
2012-05-14  7:36                         ` Joe Woodward
2012-05-14  7:55                           ` Tomi Valkeinen
2012-05-14 22:48                             ` Kevin Hilman
2012-05-15  7:28                               ` Tomi Valkeinen
2012-05-15 17:29                                 ` Kevin Hilman
2012-05-15 17:55                             ` Paul Walmsley
2012-05-16  9:08                               ` Tomi Valkeinen
2012-05-16  9:20                                 ` Tomi Valkeinen
2012-05-24 16:19                                   ` Paul Walmsley
2012-05-16 10:09                                 ` Cousson, Benoit
2012-05-24 12:35                                   ` Tomi Valkeinen
2012-05-25  0:39                                 ` Paul Walmsley
2012-05-25  8:24                                   ` Tomi Valkeinen
2012-05-25 12:55                                     ` Jean Pihet
2012-06-12 10:15                                       ` Joe Woodward
2012-06-12 10:37                                         ` Tomi Valkeinen
2012-06-12 10:50                                           ` Joe Woodward
2012-06-12 11:05                                             ` 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=1336143500.2552.23.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=a0393947@ti.com \
    --cc=jw@terrafix.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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