doc: fix typo in multiple directories (build, hardware, kernel, project)
Utilize a code spell-checking tool to scan for and correct spelling errors in all files within the doc/build, hardware, kernel, project directory. Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
This commit is contained in:
parent
accea5eb69
commit
512dc9ff38
|
@ -27,7 +27,7 @@ requires little more than implementing power management
|
||||||
and configuration for the specific GNSS modem.
|
and configuration for the specific GNSS modem.
|
||||||
|
|
||||||
Adding support for GNSS modems which use other protocols and/or
|
Adding support for GNSS modems which use other protocols and/or
|
||||||
busses than the usual NMEA0183 over UART is possible, but will
|
buses than the usual NMEA0183 over UART is possible, but will
|
||||||
require a bit more work from the driver developer.
|
require a bit more work from the driver developer.
|
||||||
|
|
||||||
Configuration Options
|
Configuration Options
|
||||||
|
|
|
@ -303,7 +303,7 @@ the controller.
|
||||||
I\ :sup:`2`\ C Devices under I3C Bus
|
I\ :sup:`2`\ C Devices under I3C Bus
|
||||||
====================================
|
====================================
|
||||||
|
|
||||||
Since I3C is backware compatible with I\ :sup:`2`\ C, the I3C controller
|
Since I3C is backward compatible with I\ :sup:`2`\ C, the I3C controller
|
||||||
API can accommodate I2C API calls without modifications if the controller
|
API can accommodate I2C API calls without modifications if the controller
|
||||||
device driver implements the I2C API. This has the advantage of using
|
device driver implements the I2C API. This has the advantage of using
|
||||||
existing I2C devices without any modifications to their device drivers.
|
existing I2C devices without any modifications to their device drivers.
|
||||||
|
|
2
doc/kernel/drivers/device_driver_model.svg
generated
2
doc/kernel/drivers/device_driver_model.svg
generated
File diff suppressed because one or more lines are too long
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
|
@ -175,7 +175,7 @@ will be ignored and the minimum value will be used instead.
|
||||||
To force a smaller than minimum value to be used, the application may enable the
|
To force a smaller than minimum value to be used, the application may enable the
|
||||||
:kconfig:option:`CONFIG_HEAP_MEM_POOL_IGNORE_MIN` option. This can be useful
|
:kconfig:option:`CONFIG_HEAP_MEM_POOL_IGNORE_MIN` option. This can be useful
|
||||||
when optimizing the heap size and the minimum requirement can be more accurately
|
when optimizing the heap size and the minimum requirement can be more accurately
|
||||||
determined for a speficic application.
|
determined for a specific application.
|
||||||
|
|
||||||
Allocating Memory
|
Allocating Memory
|
||||||
=================
|
=================
|
||||||
|
|
|
@ -302,7 +302,7 @@ registers only when :c:func:`arch_switch` is called to minimize context
|
||||||
switching latency. Such architectures must use NULL as the argument to
|
switching latency. Such architectures must use NULL as the argument to
|
||||||
:c:func:`z_get_next_switch_handle` to determine if there is a new thread
|
:c:func:`z_get_next_switch_handle` to determine if there is a new thread
|
||||||
to schedule, and follow through with their own :c:func:`arch_switch` or
|
to schedule, and follow through with their own :c:func:`arch_switch` or
|
||||||
derrivative if so, or directly leave interrupt mode otherwise.
|
derivative if so, or directly leave interrupt mode otherwise.
|
||||||
In the former case it is up to that switch code to store the handle
|
In the former case it is up to that switch code to store the handle
|
||||||
resulting from the thread that is being switched out in that thread's
|
resulting from the thread that is being switched out in that thread's
|
||||||
"switch_handle" field after its context has fully been saved.
|
"switch_handle" field after its context has fully been saved.
|
||||||
|
|
|
@ -323,7 +323,7 @@ Fix for an issue blocking development.
|
||||||
|
|
||||||
* *Maintainer*
|
* *Maintainer*
|
||||||
|
|
||||||
Maintainer review reqiured.
|
Maintainer review required.
|
||||||
|
|
||||||
* *Security Review*
|
* *Security Review*
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue