On Thu, May 27, 2010 at 11:43 PM, Pavel Machek <pavel@xxxxxx> wrote: > Hi! > >> >> >> How often would we retry suspending? >> >> > >> >> > Well based on some timer, the same way the screen blanks? Or five >> >> > seconds of no audio play? So if the suspend fails, then reset whatever >> >> > userspace suspend policy timers. >> >> > >> >> >> If we fail to suspend, don't we have to resume all the drivers that >> >> >> suspended before the one that failed? (Maybe I'm mistaken here) >> >> > >> >> > Sure, but I guess that should be a rare event that only happens when >> >> > you try to suspend and something interrupts the suspend. >> >> > >> >> >> >> This is not a rare event. For example, the matrix keypad driver blocks >> >> suspend when a key is down so it can scan the matrix. >> > >> > Sure, but how many times per day are you suspending? >> >> How many times we successfully suspend is irrelevant here. If the >> driver blocks suspend the number of suspend attempts depend on your >> poll frequency. > > Actually, this is quite interesting question I'd like answer here: > > "Sure, but how many times per day are you suspending?" > > I suspect it may be in 1000s, but it would be cool to get better > answer -- so that people knew what we are talking about here. This is highly variable. 1000s would mean that you wake about once every minute which is not uncommon, but more often than what typically happens on an idle device. The nexus one has to wake up every 10 minutes to check the battery status check means your at least in the 100s, but the G1 could stay suspended for much longer than that. The original question was about a driver blocking suspend though, and if we were to just retry suspend until it succeeds in that case you could easily get to 100000s suspend attempts in a day. -- Arve Hjønnevåg -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html