[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20141009090252.GS10832@worktop.programming.kicks-ass.net>
Date: Thu, 9 Oct 2014 11:02:52 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Mike Turquette <mturquette@...aro.org>
Cc: Morten Rasmussen <morten.rasmussen@....com>,
"mingo@...hat.com" <mingo@...hat.com>,
Dietmar Eggemann <Dietmar.Eggemann@....com>,
"pjt@...gle.com" <pjt@...gle.com>,
"bsegall@...gle.com" <bsegall@...gle.com>,
"vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
"nicolas.pitre@...aro.org" <nicolas.pitre@...aro.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tuukka.tikkanen@...aro.org" <tuukka.tikkanen@...aro.org>
Subject: Re: [PATCH RFC 2/2] cpufreq: arm_big_little: provide cpu capacity
On Wed, Oct 08, 2014 at 03:37:32PM -0700, Mike Turquette wrote:
> It creates a dependency such that any ARM platform that wants to have
> frequency-invariant load must use CPUfreq. I don't think we want that
> dependency. CPUfreq is a likely back-end for many devices, but not all.
>
> Consider near-future ARM devices that support ACPI for power management
> with no corresponding CPUfreq driver. For example if the CPPC driver is
> not hooked up to CPUfreq, platforms using CPPC will not jive with the
> ARM arch hook that depends on CPUfreq.
Oh crap no, CPPC will not add yet another interface to cpu frequency
stuff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists