summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYuval Peress <peress@chromium.org>2021-04-06 13:12:25 -0600
committerCommit Bot <commit-bot@chromium.org>2021-04-07 06:03:44 +0000
commit7cfebd9092bb2b8f36187bcd482208668dcc3a65 (patch)
treea18bb2da354fcf66289b85becc2fb8cd1c27f8c5
parent2ea0707aed5b740421956cc9fdf197e1e3d9aecd (diff)
downloadchrome-ec-7cfebd9092bb2b8f36187bcd482208668dcc3a65.tar.gz
zephyr: kconfig: move throttle_ap configs to separate file
Clean up the root Kconfig for Zephyr by moving sub configs to separate file (Kconfig.throttle_ap). BRANCH=none BUG=none TEST=zmake testall Signed-off-by: Yuval Peress <peress@chromium.org> Change-Id: I78097f824a95ecce1bf588a27c0c600e31e127b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2808151 Reviewed-by: Simon Glass <sjg@chromium.org>
-rw-r--r--zephyr/Kconfig30
-rw-r--r--zephyr/Kconfig.throttle_ap32
2 files changed, 33 insertions, 29 deletions
diff --git a/zephyr/Kconfig b/zephyr/Kconfig
index 2aff7bab6f..1f7c31ba7c 100644
--- a/zephyr/Kconfig
+++ b/zephyr/Kconfig
@@ -52,6 +52,7 @@ rsource "Kconfig.stacks"
rsource "Kconfig.system"
rsource "Kconfig.tasks"
rsource "Kconfig.temperature"
+rsource "Kconfig.throttle_ap"
rsource "Kconfig.usbc"
# Define PLATFORM_EC_... options to enable EC features. Each Kconfig should be
@@ -477,35 +478,6 @@ config PLATFORM_EC_THROTTLE_AP
a lower speed. This reduce the CPU's power output and eventually
results in a lower temperature.
-if PLATFORM_EC_THROTTLE_AP
-
-# TODO(b/177676794): Add the CONFIG_THROTTLE_AP_ON_... options
-
-config PLATFORM_EC_CHIPSET_CAN_THROTTLE
- bool "CPU can support throttling"
- default y
- help
- Indicates that the SoC supports throttling. This means that a
- chipset_throttle_cpu() function is provided by the chipset, to be
- called to set the throttle state. The typical implementation asserts
- GPIO_CPU_PROCHOT, to make the CPU slow down.
-
-config PLATFORM_EC_CONSOLE_CMD_APTHROTTLE
- bool "Console command: apthrottle"
- default y
- help
- This command shows the current status of AP throttling. Both soft
- (type 0) and hard (type 1) throttling are supported. Soft throttling
- is typically controlled by the AP via a host event. Hard throttling
- typically uses the PROCHOT (Processor Hot) signal on x86 CPUs.
-
- Example output:
-
- AP throttling type 0 is off (0x00000000)
- AP throttling type 1 is off (0x00000000)
-
-endif # PLATFORM_EC_THROTTLE_AP
-
menuconfig PLATFORM_EC_TIMER
bool "Timer module"
default y
diff --git a/zephyr/Kconfig.throttle_ap b/zephyr/Kconfig.throttle_ap
new file mode 100644
index 0000000000..153aefd085
--- /dev/null
+++ b/zephyr/Kconfig.throttle_ap
@@ -0,0 +1,32 @@
+# Copyright 2021 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+if PLATFORM_EC_THROTTLE_AP
+
+# TODO(b/177676794): Add the CONFIG_THROTTLE_AP_ON_... options
+
+config PLATFORM_EC_CHIPSET_CAN_THROTTLE
+ bool "CPU can support throttling"
+ default y
+ help
+ Indicates that the SoC supports throttling. This means that a
+ chipset_throttle_cpu() function is provided by the chipset, to be
+ called to set the throttle state. The typical implementation asserts
+ GPIO_CPU_PROCHOT, to make the CPU slow down.
+
+config PLATFORM_EC_CONSOLE_CMD_APTHROTTLE
+ bool "Console command: apthrottle"
+ default y
+ help
+ This command shows the current status of AP throttling. Both soft
+ (type 0) and hard (type 1) throttling are supported. Soft throttling
+ is typically controlled by the AP via a host event. Hard throttling
+ typically uses the PROCHOT (Processor Hot) signal on x86 CPUs.
+
+ Example output:
+
+ AP throttling type 0 is off (0x00000000)
+ AP throttling type 1 is off (0x00000000)
+
+endif # PLATFORM_EC_THROTTLE_AP