From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antti P Miettinen Subject: Re: [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params Date: Thu, 19 Jan 2012 08:49:09 +0200 Message-ID: <871uqwqja2.fsf@amiettinen-lnx.nvidia.com> References: <1326697201-32406-1-git-send-email-amiettinen@nvidia.com> <201201162238.57556.rjw@sisk.pl> <20120118031319.GB27153@mgross-G62> <201201190024.27022.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm@lists.linux-foundation.org Cc: cpufreq@vger.kernel.org List-Id: linux-pm@vger.kernel.org "Rafael J. Wysocki" writes: [..] > Perhaps we need a new cpufreq governor that would take use PM QoS internally > to store requests from different sources, but that would work on a per-CPU > basis (not globally) and would provide a new interface for user space? > > Rafael I think it would be nice if the choice of governor could be independent of the constraints. Also, implementing the constraints in the cpufreq core is easier than in governors. --Antti