From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [linux-pm] [PATCH 02/11] PM: extend PM QoS with per-device wake-up constraints Date: Sat, 20 Aug 2011 18:04:03 +0100 Message-ID: <20110820170403.GA27040@opensource.wolfsonmicro.com> References: <20110820062543.GA5011@opensource.wolfsonmicro.com> <20110820152959.GA22424@opensource.wolfsonmicro.com> <201108201834.34741.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from opensource.wolfsonmicro.com ([80.75.67.52]:55997 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753394Ab1HTREH (ORCPT ); Sat, 20 Aug 2011 13:04:07 -0400 Content-Disposition: inline In-Reply-To: <201108201834.34741.rjw@sisk.pl> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Rafael J. Wysocki" Cc: Alan Stern , Linux PM mailing list , linux-omap@vger.kernel.org, Jean Pihet , markgross@thegnar.org On Sat, Aug 20, 2011 at 06:34:34PM +0200, Rafael J. Wysocki wrote: > On Saturday, August 20, 2011, Mark Brown wrote: > > Any sort of media streaming would be an obvious example - the > > application picks the amount of data it buffers and how often it's > > notified of progress depending on the usage which then controls how > > quickly the system needs to handle things. > Well, what about other types of devices? Other than the input case (which is a latency issue - there's two components, one is how much data is delivered for things like touchscreens which stream and the other is how quickly the first data is delivered) nothing immediately springs to mind but this may just be a product of what I'm most familiar with. I don't really see this as a problem, for a lot of devices it's probably the case that the device can figure out something sensible to do without any help.