linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	"jaswinder.singh@linaro.org" <jaswinder.singh@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
	"patches@linaro.org" <patches@linaro.org>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>
Subject: Re: [PATCH v7 5/8] CPPC: Add a CPUFreq driver for use with CPPC
Date: Tue, 21 Jul 2015 09:52:14 +0100	[thread overview]
Message-ID: <55AE083E.80303@arm.com> (raw)
In-Reply-To: <3774934.MfIr66XDWO@vostro.rjw.lan>



On 20/07/15 23:07, Rafael J. Wysocki wrote:
> On Monday, July 20, 2015 03:22:09 PM Sudeep Holla wrote:
>>
>> On 09/07/15 19:04, Ashwin Chaugule wrote:
>>> This driver utilizes the methods introduced in the previous
>>> patch - "ACPI: Introduce CPU performance controls using CPPC"
>>> and enables usage with existing CPUFreq governors.
>>>
>>> Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
>>> Reviewed-by: Al Stone <al.stone@linaro.org>
>>> ---
>>>    drivers/cpufreq/Kconfig.arm    |  16 ++++
>>>    drivers/cpufreq/Makefile       |   2 +
>>>    drivers/cpufreq/cppc_cpufreq.c | 197 +++++++++++++++++++++++++++++++++++++++++
>>>    3 files changed, 215 insertions(+)
>>>    create mode 100644 drivers/cpufreq/cppc_cpufreq.c
>>>
>>> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
>>> index 4f3dbc8..578384d 100644
>>> --- a/drivers/cpufreq/Kconfig.arm
>>> +++ b/drivers/cpufreq/Kconfig.arm
>>> @@ -272,3 +272,19 @@ config ARM_PXA2xx_CPUFREQ
>>>    	  This add the CPUFreq driver support for Intel PXA2xx SOCs.
>>>
>>>    	  If in doubt, say N.
>>> +
>>> +config ACPI_CPPC_CPUFREQ
>>> +	tristate "CPUFreq driver based on the ACPI CPPC spec"
>>> +	depends on ACPI_CPPC_LIB
>>> +	default n
>>> +	help
>>> +	  This adds a CPUFreq driver which uses CPPC methods
>>> +	  as described in the ACPIv5.1 spec. CPPC stands for
>>> +	  Collaborative Processor Performance Controls. It
>>> +	  is based on an abstract continuous scale of CPU
>>> +	  performance values which allows the remote power
>>> +	  processor to flexibly optimize for power and
>>> +	  performance. CPPC relies on power management firmware
>>> +	  for its operation.
>>
>> Why is this ARM specific ? It might be used only on ARM but doesn't mean
>> it should be visible only on ARM ACPI systems.
>
> Why bother people with considering Kconfig options that are useless to them?
>

I agree to some extent, but main worry is that we are then making these
features architecture specific while ACPI is supposed to be architecture
agnostic. I was just trying to avoid doing so.

Regards,
Sudeep

  reply	other threads:[~2015-07-21  8:52 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 18:04 [PATCH v7 0/8] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 1/8] PCC: Initialize PCC Mailbox earlier at boot Ashwin Chaugule
2015-07-20 14:20   ` Sudeep Holla
2015-08-03 17:37     ` Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 2/8] ACPI: Split out ACPI PSS from ACPI Processor driver Ashwin Chaugule
2015-07-18  0:01   ` Rafael J. Wysocki
2015-07-18  0:03     ` Rafael J. Wysocki
2015-08-03 17:26       ` Ashwin Chaugule
2015-08-03 17:24     ` Ashwin Chaugule
2015-07-20 14:20   ` Sudeep Holla
2015-07-20 21:59     ` Rafael J. Wysocki
2015-08-03 17:49       ` Ashwin Chaugule
2015-08-03 17:29     ` Ashwin Chaugule
2015-08-04 14:50       ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 3/8] ACPI: Decouple ACPI idle and ACPI processor drivers Ashwin Chaugule
2015-07-20 14:21   ` Sudeep Holla
2015-08-03 17:40     ` Ashwin Chaugule
2015-08-04 14:51       ` Sudeep Holla
2015-08-04 14:58         ` Ashwin Chaugule
2015-08-04 15:18           ` Sudeep Holla
2015-08-04 15:44             ` Ashwin Chaugule
2015-08-04 17:00               ` Sudeep Holla
2015-08-05 13:47                 ` Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 4/8] ACPI: Introduce CPU performance controls using CPPC Ashwin Chaugule
2015-08-04 15:06   ` Sudeep Holla
2015-08-04 15:38     ` Ashwin Chaugule
2015-08-04 16:02       ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 5/8] CPPC: Add a CPUFreq driver for use with CPPC Ashwin Chaugule
2015-07-20 14:22   ` Sudeep Holla
2015-07-20 22:07     ` Rafael J. Wysocki
2015-07-21  8:52       ` Sudeep Holla [this message]
2015-07-21 14:27         ` Rafael J. Wysocki
2015-07-21 15:32           ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 6/8] ACPI: Add weak routines for ACPI CPU Hotplug Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 7/8] CPPC: Probe for CPPC tables for each ACPI Processor object Ashwin Chaugule
2015-07-20 14:22   ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 8/8] PCC: Enable PCC only when needed Ashwin Chaugule
2015-07-20 14:22   ` Sudeep Holla
2015-07-20 22:04     ` Rafael J. Wysocki
2015-07-21  9:23       ` Sudeep Holla
2015-07-21 14:34         ` Rafael J. Wysocki
2015-07-21 15:28           ` Sudeep Holla
2015-07-22  1:28             ` Rafael J. Wysocki
2015-07-22  8:59               ` Sudeep Holla
2015-08-03 17:35               ` Ashwin Chaugule
2015-08-04 14:53                 ` Sudeep Holla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55AE083E.80303@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=ashwin.chaugule@linaro.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).