On Mon, 9 Jan 2012, Joe Woodward wrote: > I'm running on a Gumstix Overo (OMAP3530) with an 24-bit LCD panel connected via the DPI interface (using the generic panel driver). > > Entering standby used to work just fine on 3.0, but on 3.2 I get the following: > > # echo mem > /sys/power/state ... > [ 24.466674] ------------[ cut here ]------------ > [ 24.466857] WARNING: at drivers/video/omap2/dss/dss.c:713 0xc01350f8() ... > At which point the screen either restarts, or sometimes flickers and I get the following: > [ 22.578796] omapdss DISPC error: SYNC_LOST on channel lcd, restarting the output with video overlays disabled > [ 23.391571] omapdss DISPC error: SYNC_LOST on channel lcd, restarting the output with video overlays disabled > [ 24.391571] omapdss DISPC error: SYNC_LOST on channel lcd, restarting the output with video overlays disabled > > It normally recovers after doing this for a while... > > Anyone have any ideas? Consider cc'ing the DSS maintainers and linux-fbdev list: OMAP DISPLAY SUBSYSTEM and FRAMEBUFFER SUPPORT (DSS2) M: Tomi Valkeinen <tomi.valkeinen@xxxxxx> L: linux-omap@xxxxxxxxxxxxxxx L: linux-fbdev@xxxxxxxxxxxxxxx S: Maintained F: drivers/video/omap2/ F: Documentation/arm/OMAP/DSS - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
