Searched refs:some (Results 76 – 100 of 591) sorted by relevance
12345678910>>...24
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.xtensa | 22 interrupt priorities associated with each timer, and some of
|
| /Zephyr-latest/boards/shields/wnc_m14a2a/boards/ |
| D | nrf52840dk_nrf52840.overlay | 29 * WNC-M14A2A shield uses an odd UART available on *some* Arduino-R3-compatible
|
| /Zephyr-latest/samples/boards/intel/adsp/code_relocation/ |
| D | README.rst | 12 sections TEXT, DATA and BSS be contiguous, some work is done in the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 12 Configuration Client can communicate with to change the node configuration. In some
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.native_posix | 22 Disabling this feature allows some other component to seed the host standard library random
|
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | sysbuild.cmake | 22 # This is required because some primary cores need information from the
|
| /Zephyr-latest/tests/boards/mec15xxevb_assy6853/i2c_api/ |
| D | README.txt | 15 We need to change to use I2C01 port by making some jumpers setting as below:
|
| /Zephyr-latest/samples/shields/npm6001_ek/doc/ |
| D | index.rst | 50 find some command examples.
117 GPIO functionality offered by the PMIC. Below you can find some command
158 Watchdog functionality offered by the PMIC. Below you can find some command
|
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 10 For some boards `src/main.c` may also need to be extended to configure
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | shared_multi_heap.rst | 16 1. At boot time some platform code initialize the shared multi-heap framework
59 3. When a driver or application needs some dynamic memory with a certain
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 19 timeout is checked may be some time after it should have expired. Handling
55 in some applications, as it does allow a millisecond-resolution calculation of
|
| /Zephyr-latest/tests/boards/mec172xevb_assy6906/i2c_api/ |
| D | README.txt | 15 We need to change to use I2C01 port by making some jumpers setting as below:
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 33 array, so that they can be started independently in gdb, valgrind or some other
61 BabbleSim platform, but with some mesh specific additions:
82 This includes ``PASS``/``FAIL`` macros and some common mesh actions, such as
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | gmap.rst | 40 supports the role (the GMAP roles depend on some BAP configurations).
46 (some logging has been omitted for clarity):
|
| /Zephyr-latest/samples/drivers/led/xec/ |
| D | README.rst | 54 to VTR or some other power source.
63 to VTR or some other power source.
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.timer | 76 bool "Support timeouts for some blocking POSIX services"
78 Enable mandatory timeouts for some blocking operations.
|
| /Zephyr-latest/drivers/syscon/ |
| D | Kconfig | 15 of device. The typical use-case is for some other node's driver, or
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.esp32 | 22 Enable the built-in USB serial interface present in some Espressif
|
| /Zephyr-latest/tests/drivers/can/timing/ |
| D | Kconfig | 10 controllers can meet all of the bitrates listed below, and some board configurations may
|
| /Zephyr-latest/subsys/storage/stream/ |
| D | Kconfig | 21 allows to save some code storage and RAM.
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-syntax-structure.rst | 14 understand some detailed cases.
67 Property values can be any sequence of bytes. In some cases, the values are an
79 In practice, devicetree nodes usually correspond to some hardware, and the node
169 address space of its parent node. Here are some example unit addresses for
259 Here are some common patterns:
270 You may notice some similarities between the ``reg`` property and common
296 of one or more *interrupt specifiers*. Each interrupt specifier has some
314 properties continue to persist for historical reasons in some existing
367 - ``some-phandles = <&mynode0 &mynode1 &mynode2>;``
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 39 a HW agnostic test platform which in some cases utilizes the host OS
71 Otherwise `with some tinkering
81 The underlying assumptions behind this port set some limitations on what
150 some part of that loop.
159 interrupt, or a call to :c:func:`k_busy_wait` with some small delay in
237 instruction executes is just some of it; Emulating peripherals accurately
268 Depending on configuration, QEMU also provides models of some peripherals
269 and, in some cases, can expose host HW as emulated target peripherals.
281 Execution is not reproducible. Some bugs may be triggered only in some runs
289 and some or all peripherals too.
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 30 will be declared in some header under ``include/`` or in another
62 The :ref:`parse_syscalls.py` script does some parsing of the function prototype,
63 to determine the data types of its return value and arguments, and has some
141 Declaring an API with :c:macro:`__syscall` causes some code to be generated in
245 declared in some C file. There is no prototype needed for implementation
274 made simpler by some macros in :zephyr_file:`include/zephyr/internal/syscall_handler.h`.
312 * :c:macro:`K_SYSCALL_VERIFY_MSG()` does a runtime check of some boolean
335 calling thread. This is done instead of returning some error condition to
391 for some integral value:
421 memory as part of its logic. For example, it could be used to store some
[all …]
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 6 Thread support is not necessary in some applications:
77 expected to work to some degree when :kconfig:option:`CONFIG_MULTITHREADING` is
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 8 external tool. In some configurations, ``west sign`` is also used to invoke
27 difficult. Reproducing a lower ``west sign`` command to debug some build-time issue
|
12345678910>>...24
