Home
last modified time | relevance | path

Searched full:consistent (Results 1 – 25 of 99) sorted by relevance

1234

/Zephyr-latest/include/zephyr/portability/
Dcmsis_os.h54 /// \note MUST REMAIN UNCHANGED: \b osKernelSystemId shall be consistent in every CMSIS-RTOS.
57 /// \note MUST REMAIN UNCHANGED: \b osFeature_xxx shall be consistent in every CMSIS-RTOS.
81 /// \note MUST REMAIN UNCHANGED: \b osPriority shall be consistent in every CMSIS-RTOS.
94 /// \note MUST REMAIN UNCHANGED: \b osWaitForever shall be consistent in every CMSIS-RTOS.
98 /// \note MUST REMAIN UNCHANGED: \b osStatus shall be consistent in every CMSIS-RTOS.
119 /// \note MUST REMAIN UNCHANGED: \b os_timer_type shall be consistent in every CMSIS-RTOS.
126 /// \note MUST REMAIN UNCHANGED: \b os_pthread shall be consistent in every CMSIS-RTOS.
130 /// \note MUST REMAIN UNCHANGED: \b os_ptimer shall be consistent in every CMSIS-RTOS.
225 /// \note MUST REMAIN UNCHANGED: \b os_event shall be consistent in every CMSIS-RTOS.
245 /// \note MUST REMAIN UNCHANGED: \b osKernelInitialize shall be consistent in every CMSIS-RTOS.
[all …]
/Zephyr-latest/include/zephyr/sys/
Dbarrier.h35 * @brief Full/sequentially-consistent data memory barrier.
48 * @brief Full/sequentially-consistent data synchronization barrier.
57 * back to a full/sequentially-consistent data memory barrier.
67 * @brief Full/sequentially-consistent instruction synchronization barrier.
/Zephyr-latest/tests/lib/c_lib/strerror/src/
Dmain.c32 /* consistent behaviour w.r.t. errno with invalid input */ in ZTEST()
45 /* consistent behaviour for "Success" */ in ZTEST()
/Zephyr-latest/
D.yamllint12 indent-sequences: consistent
/Zephyr-latest/tests/drivers/uart/uart_mix_fifo_poll/
DREADME.txt17 data is consistent.
/Zephyr-latest/cmake/toolchain/cross-compile/
Dgeneric.cmake12 # prefix. This interface is consistent with the other non-"Zephyr SDK"
/Zephyr-latest/subsys/logging/
DKconfig.template.log_format_config35 # The numbering of the format types should be consistent across
/Zephyr-latest/dts/bindings/dma/
Dnxp,edma.yaml32 # be consistent in this regard.
/Zephyr-latest/dts/bindings/pinctrl/
Dambiq,apollo3-pinctrl.yaml116 0 here to make it be consistent with AM_HAL_GPIO_PINCFG_DEFAULT in
126 0 here to make it be consistent with AM_HAL_GPIO_PINCFG_DEFAULT in
/Zephyr-latest/samples/tfm_integration/psa_crypto/src/
Dutil_app_cfg.h18 * The first 6 bytes of this struct should remain consistent in any future
/Zephyr-latest/dts/bindings/timer/
Dst,stm32-lptim.yaml53 Valid range is [1, 256] and should be consistent with st,prescaler
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst32 Maintain consistency across all requirements. The language and choice of words shall be consistent.
109 * Consistent
/Zephyr-latest/include/zephyr/drivers/usb/
Dudc_buf.h20 * Here we try to get DMA-safe buffers, but we lack a consistent source of
22 * consistent source of information about what part of memory is DMA'able.
/Zephyr-latest/.github/workflows/
Dtwister-publish.yaml41 # set run date on upload to get consistent and unified data across the matrix.
/Zephyr-latest/subsys/pm/
Dstate.c39 /* Check that all power states are consistent */
/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/
Ddoxytooltip.css3 look and feel that's consistent with the rest of the documentation without necessarily aiming
/Zephyr-latest/doc/contribute/
Dproposals_and_rfcs.rst12 The "RFC" (request for comments) process is intended to provide a consistent and
/Zephyr-latest/doc/develop/languages/c/
Dminimal_libc.rst56 error numbers consistent with the different implementations of the C standard
/Zephyr-latest/doc/introduction/
Dindex.rst119 Provides a consistent device model for configuring the drivers that are part
120 of the platform/system and a consistent model for initializing all the
/Zephyr-latest/doc/hardware/porting/
Dshields.rst32 the default shield configuration here should be consistent with those in
36 is made to be consistent with the :ref:`default_board_configuration`. Hence,
/Zephyr-latest/doc/project/
Ddocumentation.rst51 needs to follow a new structure to avoid confusion. Using a consistent naming
/Zephyr-latest/include/zephyr/fs/
Dlittlefs.h72 * values are consistent with littlefs requirements.
/Zephyr-latest/tests/lib/json/src/
Dmain.c287 zassert_equal(ret, 0, "Encoded contents not consistent"); in ZTEST()
450 "Encoded array of objects is not consistent"); in ZTEST()
525 "Encoded array of objects is not consistent"); in ZTEST()
601 "Encoded array of objects is not consistent"); in ZTEST()
730 "Encoded two-dimensional array is not consistent"); in ZTEST()
813 "Encoded two-dimensional extra array is not consistent"); in ZTEST()
897 "Encoded two-dimensional extra named array is not consistent"); in ZTEST()
1333 zassert_mem_equal(buffer, encoded, sizeof(encoded), "Encoded contents not consistent"); in ZTEST()
/Zephyr-latest/include/zephyr/net/
Dtrickle.h115 * @brief To be called by the protocol handler when it hears a consistent
/Zephyr-latest/doc/kernel/services/other/
Datomic.rst96 instructions on x86, "DMB" on ARM, or a "sequentially consistent"

1234