Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755618AbYFBQo5 (ORCPT ); Mon, 2 Jun 2008 12:44:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753252AbYFBQou (ORCPT ); Mon, 2 Jun 2008 12:44:50 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:34150 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753243AbYFBQot (ORCPT ); Mon, 2 Jun 2008 12:44:49 -0400 Date: Mon, 2 Jun 2008 17:44:35 +0100 From: Matthew Garrett To: Henrique de Moraes Holschuh Cc: Roger Heflin , Arjan van de Ven , Guntsche Michael , linux-kernel@vger.kernel.org Subject: Re: 2.6.25.x: Wrong CPU frequency (cpufreq table) with p4-clockmod Message-ID: <20080602164434.GA14012@srcf.ucam.org> References: <12C649C0-4BEF-41F1-B738-8C8CEF8AEBB8@it-loops.com> <20080530065717.44cf7414@infradead.org> <20080601185643.3d3db64f@infradead.org> <48435CCA.5000905@gmail.com> <20080602153759.GA3406@khazad-dum.debian.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080602153759.GA3406@khazad-dum.debian.net> User-Agent: Mutt/1.5.12-2006-07-14 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 677 Lines: 17 On Mon, Jun 02, 2008 at 12:37:59PM -0300, Henrique de Moraes Holschuh wrote: > Indeed. And if we had a generic interface for throttling (ACPI > T-states-like) and frequency changes (ACPI P-states-like), we could just > move p4-clockmod to the throttling one (and NOT letting it register with > the frequency changes interface), and be done with it. > > Do we have these interfaces? No. -- Matthew Garrett | mjg59@srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/