Kconfig 1.6 KB

123456789101112131415161718192021222324252627282930313233
  1. menu "IPC (Inter-Processor Call)"
  2. config ESP_IPC_TASK_STACK_SIZE
  3. int "Inter-Processor Call (IPC) task stack size"
  4. range 512 65536 if !APPTRACE_ENABLE
  5. range 2048 65536 if APPTRACE_ENABLE
  6. default 2048 if APPTRACE_ENABLE
  7. default 1536
  8. help
  9. Configure the IPC tasks stack size. An IPC task runs on each core (in dual core mode), and allows for
  10. cross-core function calls. See IPC documentation for more details. The default IPC stack size should be
  11. enough for most common simple use cases. However, users can increase/decrease the stack size to their
  12. needs.
  13. config ESP_IPC_USES_CALLERS_PRIORITY
  14. bool "IPC runs at caller's priority"
  15. default y
  16. depends on !FREERTOS_UNICORE
  17. help
  18. If this option is not enabled then the IPC task will keep behavior same as prior to that of ESP-IDF v4.0,
  19. hence IPC task will run at (configMAX_PRIORITIES - 1) priority.
  20. config ESP_IPC_ISR_ENABLE
  21. bool
  22. default y if !FREERTOS_UNICORE
  23. help
  24. The IPC ISR feature is similar to the IPC feature except that the callback function is executed in the
  25. context of a High Priority Interrupt. The IPC ISR feature is itended for low latency execution of simple
  26. callbacks written in assembly on another CPU. Due to being run in a High Priority Interrupt, the assembly
  27. callbacks must be written with particular restrictions (see "IPC" and "High-Level Interrupt" docs for more
  28. details).
  29. endmenu # "IPC (Inter-Processor Call)