From: Ashwin Chaugule <ashwin.chaugule@linaro.org>
To: rjw@rjwysocki.net, jaswinder.singh@linaro.org
Cc: linux-pm@vger.kernel.org, linaro-acpi@lists.linaro.org,
patches@linaro.org, linux-acpi@vger.kernel.org,
viresh.kumar@linaro.org, sudeep.holla@arm.com,
Ashwin Chaugule <ashwin.chaugule@linaro.org>
Subject: [PATCH v6 6/7] PCC: Enable PCC only when needed
Date: Mon, 15 Jun 2015 16:09:10 -0400 [thread overview]
Message-ID: <56fc29c35e139eaa1733c9c29073339fabf93956.1434398373.git.ashwin.chaugule@linaro.org> (raw)
In-Reply-To: <cover.1434398373.git.ashwin.chaugule@linaro.org>
In-Reply-To: <cover.1434398373.git.ashwin.chaugule@linaro.org>
CPPC is the first client to make use of the PCC Mailbox channel. So
enable it only when CPPC is also enabled.
Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Reviewed-by: Al Stone <al.stone@linaro.org>
---
drivers/mailbox/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
index 84b0a2d..60c8da6 100644
--- a/drivers/mailbox/Kconfig
+++ b/drivers/mailbox/Kconfig
@@ -45,7 +45,7 @@ config OMAP_MBOX_KFIFO_SIZE
config PCC
bool "Platform Communication Channel Driver"
- depends on ACPI
+ depends on ACPI && ACPI_CPPC
help
ACPI 5.0+ spec defines a generic mode of communication
between the OS and a platform such as the BMC. This medium
--
1.9.1
next prev parent reply other threads:[~2015-06-15 20:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 20:09 [PATCH v6 0/7] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 1/7] PCC: Initialize PCC Mailbox earlier at boot Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 2/7] ACPI: Make ACPI processor driver more extensible Ashwin Chaugule
2015-07-08 1:07 ` Rafael J. Wysocki
2015-07-08 1:27 ` Ashwin Chaugule
2015-07-08 13:34 ` Rafael J. Wysocki
2015-07-08 13:42 ` Ashwin Chaugule
2015-07-08 19:16 ` Ashwin Chaugule
2015-07-08 19:55 ` Rafael J. Wysocki
2015-07-08 20:05 ` Ashwin Chaugule
2015-07-08 20:28 ` Ashwin Chaugule
2015-07-08 20:46 ` Rafael J. Wysocki
2015-07-08 21:46 ` Ashwin Chaugule
2015-07-08 22:21 ` Rafael J. Wysocki
2015-07-08 21:57 ` Ashwin Chaugule
2015-07-08 23:29 ` Rafael J. Wysocki
2015-07-08 23:33 ` Rafael J. Wysocki
2015-07-09 9:11 ` Sudeep Holla
2015-07-09 9:06 ` Sudeep Holla
2015-07-09 12:25 ` Ashwin Chaugule
2015-07-09 13:18 ` Sudeep Holla
2015-07-08 13:43 ` Sudeep Holla
2015-07-08 13:56 ` Ashwin Chaugule
2015-07-08 14:20 ` Sudeep Holla
2015-06-15 20:09 ` [PATCH v6 3/7] ACPI: Introduce CPU performance controls using CPPC Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 4/7] CPPC: Add a CPUFreq driver for use with CPPC Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 5/7] CPPC: Probe for CPPC tables for each ACPI Processor object Ashwin Chaugule
2015-06-15 20:09 ` Ashwin Chaugule [this message]
2015-06-15 20:09 ` [PATCH v6 7/7] ACPI: Add weak routines for ACPI CPU Hotplug Ashwin Chaugule
2015-06-29 17:23 ` [PATCH v6 0/7] CPUFreq driver using CPPC methods Ashwin Chaugule
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=56fc29c35e139eaa1733c9c29073339fabf93956.1434398373.git.ashwin.chaugule@linaro.org \
--to=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=sudeep.holla@arm.com \
--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).