From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Date: Tue, 24 Apr 2012 21:49:26 +0000 Subject: [PATCH 0/3] PM / Domains: Fix device stop and domain power off governor functions Message-Id: <201204242349.26288.rjw@sisk.pl> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Linux PM list Cc: LKML , Kevin Hilman , Magnus Damm , linux-sh@vger.kernel.org, Mark Brown , markgross@thegnar.org, Jean Pihet Hi all, It turns out that the PM domains device stop and domain power off governor functions I invented some time ago don't really make sense, because they should only decide whether or not the resulting low-power state will be too deep and that only depends on latencies. In particular, the time when devices have been suspended doesn't really matter here, so the results returned by those functions shouldn't depend on it either (as it shouldn't depend on any "break even" values that only make sense when we know how much time in advance the device is going to be used, but this information is not related to the PM QoS latency constraint). If this functions are fixed (patches [1/3] and [2/3]), then some ugly computations can be removed from rpm_suspend() and other places and the whole framework can be simplified quite a bit (patch [3/3]). Thanks, Rafael From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757867Ab2DXVrP (ORCPT ); Tue, 24 Apr 2012 17:47:15 -0400 Received: from ogre.sisk.pl ([193.178.161.156]:34999 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757026Ab2DXVrN (ORCPT ); Tue, 24 Apr 2012 17:47:13 -0400 From: "Rafael J. Wysocki" To: Linux PM list Subject: [PATCH 0/3] PM / Domains: Fix device stop and domain power off governor functions Date: Tue, 24 Apr 2012 23:49:26 +0200 User-Agent: KMail/1.13.6 (Linux/3.4.0-rc4+; KDE/4.6.0; x86_64; ; ) Cc: LKML , Kevin Hilman , Magnus Damm , linux-sh@vger.kernel.org, Mark Brown , markgross@thegnar.org, Jean Pihet MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201204242349.26288.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, It turns out that the PM domains device stop and domain power off governor functions I invented some time ago don't really make sense, because they should only decide whether or not the resulting low-power state will be too deep and that only depends on latencies. In particular, the time when devices have been suspended doesn't really matter here, so the results returned by those functions shouldn't depend on it either (as it shouldn't depend on any "break even" values that only make sense when we know how much time in advance the device is going to be used, but this information is not related to the PM QoS latency constraint). If this functions are fixed (patches [1/3] and [2/3]), then some ugly computations can be removed from rpm_suspend() and other places and the whole framework can be simplified quite a bit (patch [3/3]). Thanks, Rafael