Searched full:examined (Results 1 – 23 of 23) sorted by relevance
/Zephyr-latest/include/zephyr/arch/common/ |
D | exc_handle.h | 19 * defines start and end symbols where the memory in the string is examined;
|
/Zephyr-latest/doc/contribute/ |
D | proposals_and_rfcs.rst | 52 project in order for it to be examined during the next meeting.
|
/Zephyr-latest/dts/bindings/pinctrl/ |
D | nxp,mcux-rt11xx-pinctrl.yaml | 22 Note that the soc level iomuxc dts file can be examined to find the possible
|
D | nxp,imx8mp-pinctrl.yaml | 23 Note that the soc level iomuxc dts file can be examined to find the possible
|
D | nxp,imx7d-pinctrl.yaml | 11 Note that the soc level iomuxc dts file can be examined to find the possible
|
D | nxp,imx93-pinctrl.yaml | 23 Note that the soc level iomuxc dts file can be examined to find the possible
|
D | nxp,imx8m-pinctrl.yaml | 22 Note that the soc level iomuxc dts file can be examined to find the possible
|
D | nxp,mcux-rt-pinctrl.yaml | 23 Note that the soc level iomuxc dts file can be examined to find the possible
|
/Zephyr-latest/drivers/console/ |
D | Kconfig | 107 be examined at runtime with a debugger. Useful in board bring-up 117 examined by a debugger or software tool from a parallel-running OS.
|
/Zephyr-latest/tests/kernel/interrupt/src/ |
D | regular_isr.c | 103 * gets examined as a workaround. in ZTEST()
|
/Zephyr-latest/doc/project/ |
D | proposals.rst | 46 Items are examined for similarity with existing features, how they fit with
|
/Zephyr-latest/doc/develop/west/ |
D | why.rst | 45 examined in detail:
|
/Zephyr-latest/include/zephyr/kernel/ |
D | thread_stack.h | 449 * inside needs to be examined, examine thread->stack_info for the associated 500 * inside needs to be examined, examine thread->stack_info for the associated 529 * inside needs to be examined, examine thread->stack_info for the associated
|
/Zephyr-latest/doc/kernel/usermode/ |
D | kernelobjects.rst | 115 be prevented. When a device struct is found, its API pointer is examined to
|
/Zephyr-latest/modules/thrift/src/thrift/transport/ |
D | TSSLSocket.h | 405 * is examined.
|
/Zephyr-latest/doc/services/debugging/ |
D | coredump.rst | 50 memory content and stack can be examined in the debugger.
|
/Zephyr-latest/doc/security/standards/ |
D | etsi-303645.rst | 627 and measurement data, it should be examined for security anomalies.
|
/Zephyr-latest/arch/ |
D | Kconfig | 381 memory is examined, which is the region between the current stack
|
/Zephyr-latest/scripts/build/ |
D | gen_kobject_list.py | 28 time is also examined to disambiguate between various device driver instances
|
/Zephyr-latest/arch/x86/core/ |
D | x86_mmu.c | 1081 * parameter. This address is not directly examined, it will simply be 1152 * This region is not directly examined, it will simply be
|
/Zephyr-latest/include/zephyr/sys/ |
D | cbprintf.h | 224 * is set, list of read-write strings is examined and if they are not determined
|
/Zephyr-latest/doc/services/logging/ |
D | index.rst | 475 that log entry. Backend slots are examined when message is processed by the core
|
/Zephyr-latest/include/zephyr/ |
D | kernel.h | 1715 * (indicating that it has expired at least once since it was last examined)
|