arch: & kernel: Updated Kconfigs to remove errors in html generation
This patch updates some help sections to remove the "ERROR: Unexpected indentation" messages during hmtl documentation generation. Change-Id: Idcdc17727b921b6145f9eb28d85975ceca273ce2 Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
This commit is contained in:
parent
a81c3080a2
commit
baddeadda1
4 changed files with 8 additions and 2 deletions
|
@ -97,6 +97,7 @@ config NUM_REGULAR_IRQ_PRIO_LEVELS
|
|||
This represents the number of Regular Interrupt priorities, which
|
||||
does NOT include the Fast (FIRQ) priority.
|
||||
The Regular Interrupt priorities available will be
|
||||
|
||||
(NUM_IRQ_PRIO_LEVELS - NUM_REGULAR_IRQ_PRIO_LEVELS) to
|
||||
(NUM_REGULAR_IRQ_PRIO_LEVELS - 1).
|
||||
|
||||
|
@ -157,6 +158,7 @@ config NSIM
|
|||
default n
|
||||
help
|
||||
For running on nSIM simulator.
|
||||
|
||||
a) Uses non-XIP to run in RAM.
|
||||
b) Linked at address 0x4000 with 0x4000 of RAM so that it works with
|
||||
a pc_size of 16 (default).
|
||||
|
@ -220,6 +222,7 @@ config IRQ_VECTOR_TABLE_CUSTOM
|
|||
the least overhead when handling an interrupt.
|
||||
|
||||
Downsides:
|
||||
|
||||
- ISRs cannot have a parameter
|
||||
- ISRs cannot be connected at runtime
|
||||
- ISRs must notify the kernel manually by invoking _ExcExit() when
|
||||
|
|
|
@ -186,6 +186,7 @@ config IRQ_VECTOR_TABLE_CUSTOM
|
|||
the least overhead when handling an interrupt.
|
||||
|
||||
Downsides:
|
||||
|
||||
- ISRs cannot have a parameter
|
||||
- ISRs cannot be connected at runtime
|
||||
- ISRs must notify the kernel manually by invoking _IntExit() when
|
||||
|
|
|
@ -153,6 +153,7 @@ config KERNEL_EVENT_LOGGER_SLEEP
|
|||
help
|
||||
Enable low power condition event messages. These messages provide the
|
||||
following information:
|
||||
|
||||
- When the CPU went to sleep mode.
|
||||
- When the CPU woke up.
|
||||
- The ID of the interrupt that woke the CPU up.
|
||||
|
|
|
@ -163,6 +163,7 @@ config TASK_MONITOR_MASK
|
|||
This option specifies which task execution activities are captured
|
||||
in the task monitor's trace buffer. The following values can be
|
||||
OR-ed together to form the mask:
|
||||
|
||||
1 (MON_TSWAP): task switch
|
||||
2 (MON_STATE): task state change
|
||||
4 (MON_KSERV): task execution of kernel APIs
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue