From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH 1/3] PM / QoS: Make it possible to expose PM QoS latency constraints Date: Fri, 09 Mar 2012 09:10:58 -0800 Message-ID: <87pqcl4s4d.fsf@ti.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog133.obsmtp.com ([74.125.149.82]:54100 "EHLO psmtp.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758213Ab2CIRK5 (ORCPT ); Fri, 9 Mar 2012 12:10:57 -0500 Received: by mail-iy0-f180.google.com with SMTP id e36so3746288iag.39 for ; Fri, 09 Mar 2012 09:10:56 -0800 (PST) In-Reply-To: (Alan Stern's message of "Fri, 9 Mar 2012 10:17:32 -0500 (EST)") Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Alan Stern Cc: "Rafael J. Wysocki" , Linux PM list , Linux MMC list , Guennadi Liakhovetski , Chris Ball , Ulf Hansson , Magnus Damm , Linus Walleij , Adrian Hunter , Mark Brown Alan Stern writes: [...] > How about calling it "runtime latency"? Or "runtime wakeup latency" in > case people think there might be some other sort of latency associated > with runtime power management. Either is better than just latency, but I would vote for runtime wakeup latency. Kevin