On Sun, May 11, 2014 at 4:42 PM, Tony Lindgren [off-list ref] wrote:
* Andreas Müller [off-list ref] [140509 14:07]:
quoted
On Fri, May 9, 2014 at 9:38 AM, Tomi Valkeinen [off-list ref] wrote:
quoted
On 30/04/14 02:52, Tony Lindgren wrote:
quoted
Otherwise we can get often errors like the following and the
display won't come on:
omapdss APPLY error: FIFO UNDERFLOW on gfx, disabling the overlay
omapdss APPLY error: SYNC_LOST on channel lcd, restarting
the output with video overlays disabled
There are some earlier references to this issue:
http://www.spinics.net/lists/linux-omap/msg59511.html
http://www.spinics.net/lists/linux-omap/msg59724.html
resend - my client had HTML enabled...
FWIW: I have had issues long time ago [1]. With mainline 3.14.3 I had
still the reboot problem on old 600MHz OMAP 3530. Applying this patch
solved the issues. For other versions I had no chance to reproduce the
original wakup issue mentioned in old thread
Sorry I'm a bit confused now. Is the reboot issue a separate issue
related to the twl4030 generic scripts for 3530?
And then this patch fixes dm3730 wake-up (from suspend?) issues?
Or do we have some other bug where we wrongly hit omap3630_dss_feats
on 3530 somehow?
(What I think) I have done: Have 3.14.3 still booting with legacy
board init (please don't kill me for that). Without applying your
patch old OMAP3530 crashed at every reboot with SYNCH_LOST.
After applying your patch reboot works fine.
Looking into id-code makes me wonder what changes on 36xx-features do
to 35xx devices (treated as 34xx - right?). The only way that this
happens is for unknown hawkeye fallthough. I suggest you simply forget
my note and I will find out what really 'fixed' dss reboot problem.
Andreas