Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-04 14:53:47 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fix typos in comments and Kconfig files

Browse Source 
Signed-off-by: Juha Niskanen <juha.niskanen@haltian.com>
This commit is contained in:
Juha Niskanen
2021-12-20 16:49:48 +02:00
committed by Xiang Xiao
parent 1e83c83bf3
commit 422ceec99b
21 changed files with 45 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sched/Kconfig
+16 -24
View File
@@ -13,14 +13,6 @@ menuconfig DISABLE_OS_API
disable functions unless you want to restrict usage
of those APIs.
There are certain dependency relationships in these
features.
1) mq_notify logic depends on signals to awaken tasks
waiting for queues to become full or empty.
2) pthread_condtimedwait() depends on signals to wake
up waiting tasks.
if DISABLE_OS_API
config DISABLE_POSIX_TIMERS
@@ -63,11 +55,11 @@ config SCHED_TICKLESS
---help---
By default, system time is driven by a periodic timer interrupt. An
alternative configurations is a tick-less configuration in which
there is no periodic timer interrupt. Instead and interval timer is
there is no periodic timer interrupt. Instead an interval timer is
used to schedule the next OS time event. This option selects that
tick-less OS option. If the tick-less OS is selected, then there are
additional platform specific interfaces that must be provided as
defined include/nuttx/arch.h
defined in include/nuttx/arch.h
if SCHED_TICKLESS
@@ -605,7 +597,7 @@ config SCHED_THREAD_LOCAL
default n
depends on ARCH_HAVE_THREAD_LOCAL
---help---
This option enables architecture-sepecific TLS supports (__thread/thread_local keyword)
This option enables architecture-specific TLS support (__thread/thread_local keyword)
Note: Toolchain must be compiled with '--enable-tls' enabled
endmenu # Tasks and Scheduling
@@ -688,7 +680,7 @@ config CANCELLATION_POINTS
default n
---help---
Enable POSIX cancellation points for pthread_cancel(). If selected,
cancellation points will also used with the () task_delete() API even if
cancellation points will also used with the task_delete() API even if
pthreads are not enabled.
endmenu # Pthread Options
@@ -755,48 +747,48 @@ config SCHED_CRITMONITOR_MAXTIME_THREAD
default 0
---help---
Thread execution time should be smaller than
SCHED_CRITMONITOR_MAXTIME_THREAD, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_THREAD, or system will give a warning.
For debugging system latency, 0 means disabled.
config SCHED_CRITMONITOR_MAXTIME_WQUEUE
int "WORK queue max execution time"
default SCHED_CRITMONITOR_MAXTIME_THREAD
---help---
Worker execution time should be smaller than
SCHED_CRITMONITOR_MAXTIME_WQUEUE, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_WQUEUE, or system will give a warning.
For debugging system latency, 0 means disabled.
config SCHED_CRITMONITOR_MAXTIME_PREEMPTION
int "Pre-emption (sched_lock) max holding time"
default SCHED_CRITMONITOR_MAXTIME_WQUEUE
---help---
Pre-emption holding time should be smaller than
SCHED_CRITMONITOR_MAXTIME_PREEMPTION, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_PREEMPTION, or system will give a warning.
For debugging system latency, 0 means disabled.
config SCHED_CRITMONITOR_MAXTIME_CSECTION
int "Csection (enter_critical_section) max holding time"
default SCHED_CRITMONITOR_MAXTIME_PREEMPTION
---help---
Csection holding time should be smaller than
SCHED_CRITMONITOR_MAXTIME_CSECTION, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_CSECTION, or system will give a warning.
For debugging system latency, 0 means disabled.
config SCHED_CRITMONITOR_MAXTIME_IRQ
int "IRQ max execution time"
default SCHED_CRITMONITOR_MAXTIME_CSECTION
---help---
IRQ handler execution time should be smaller than
SCHED_CRITMONITOR_MAXTIME_IRQ, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_IRQ, or system will give a warning.
For debugging system latency, 0 means disabled.
config SCHED_CRITMONITOR_MAXTIME_WDOG
int "WDOG callback max execution time"
default SCHED_CRITMONITOR_MAXTIME_IRQ
---help---
Wdog callback execution time should be smaller than
SCHED_CRITMONITOR_MAXTIME_WDOG, or system will give a warnning.
For debugging system lantency, 0 means disabled.
SCHED_CRITMONITOR_MAXTIME_WDOG, or system will give a warning.
For debugging system latency, 0 means disabled.
endif # SCHED_CRITMONITOR