summaryrefslogtreecommitdiff
path: root/zephyr/Kconfig.defaults
diff options
context:
space:
mode:
authorPeter Marheine <pmarheine@chromium.org>2022-10-11 17:16:17 +1100
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2022-10-19 04:53:48 +0000
commitc58ec4493f1f92393aed671b96c6063646c068c7 (patch)
tree81988a7a02e3f0e07de0a497958c36d27691a818 /zephyr/Kconfig.defaults
parent2679581d743a510cdbcde68f9dd8c24a2d974c7b (diff)
downloadchrome-ec-c58ec4493f1f92393aed671b96c6063646c068c7.tar.gz
zephyr: reduce priority of shell thread
Using EC task priority alone ignores other zephyr threads and tends to give the shell thread higher priority than makes sense; higher priority than motion sensors and power sequencing for instance. Reduce the default shell thread priority to be prioritized after most threads except the work queue and idle tasks. This removes the explicit call to k_thread_priority_set in shell initialization because the EC kconfig defaults already request a custom priority by setting CONFIG_SHELL_THREAD_PRIORITY_OVERRIDE so it is redundant to set the priority again after shell_init(). BUG=b:240485526 TEST=Nereid still works normally (though performance doesn't seem improved) BRANCH=none Signed-off-by: Peter Marheine <pmarheine@chromium.org> Change-Id: I62bf4bc41da78d1d992e3bc0b762eb329fc8ea82 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3944072 Reviewed-by: Yuval Peress <peress@google.com> Code-Coverage: Zoss <zoss-cl-coverage@prod.google.com>
Diffstat (limited to 'zephyr/Kconfig.defaults')
-rw-r--r--zephyr/Kconfig.defaults2
1 files changed, 1 insertions, 1 deletions
diff --git a/zephyr/Kconfig.defaults b/zephyr/Kconfig.defaults
index ded7516748..e0992f91fa 100644
--- a/zephyr/Kconfig.defaults
+++ b/zephyr/Kconfig.defaults
@@ -29,7 +29,7 @@ config SHELL_THREAD_PRIORITY_OVERRIDE
default y
config SHELL_THREAD_PRIORITY
- default 12 # track EC_SHELL_PRIO
+ default 20
config EXTRA_EXCEPTION_INFO
default y if ARCH_HAS_EXTRA_EXCEPTION_INFO