Hi Tomi On Wed, 27 Jun 2012, Paul Walmsley wrote: > On Thu, 10 May 2012, Tomi Valkeinen wrote: > > > These patches fix DSS hwmod data related to sysc flags. I haven't seen any > > problem produced by these missing bits, but by looking at the TRM it's clear > > that they should be defined. > > > > However, applying these will cause additional warnings to show during boot: > > > > omap_hwmod: dss_dispc: softreset failed (waited 10000 usec) > > omap_hwmod: dss_rfbi: softreset failed (waited 10000 usec) > > > > Most likely the softreset fails even now, but as there's no check to verify it, > > no warnings are visible. > > > > I think the reason for the failing softreset is the same problem as we have on > > OMAP4: dss_core hwmod should be enabled before other dss hwmods can be enabled > > (and reset). > > Thanks, queued for 3.6. > > Not sure what to do about the softreset issues at the moment, due to > competing priorities. But for sure the data should match the hardware. I've dropped these for 3.6 since they cause a PM regression during a system suspend test: [ 39.721282] Powerdomain (dss_pwrdm) didn't enter target state 1 Probably before we can pull these in, we need to figure out what's going on there. - 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
