Home
last modified time | relevance | path

Searched full:mostly (Results 1 – 25 of 58) sorted by relevance

123

/Zephyr-Core-3.5.0/lib/posix/
DKconfig18 Enable mostly-standards-compliant implementations of
35 This enables a mostly-standards-compliant implementation of
/Zephyr-Core-3.5.0/tests/lib/devicetree/api_ext/
Dtestcase.yaml5 # will mostly likely be the fastest.
/Zephyr-Core-3.5.0/tests/lib/devicetree/api/
Dtestcase.yaml5 # will mostly likely be the fastest.
/Zephyr-Core-3.5.0/tests/lib/devicetree/devices/
Dtestcase.yaml5 # will mostly likely be the fastest.
/Zephyr-Core-3.5.0/boards/posix/nrf_bsim/common/
Dcmdline.h14 * They are therefore mostly equal except for types and functions names.
/Zephyr-Core-3.5.0/dts/bindings/gpio/
Darduino-nano-header-r3.yaml9 * A 15-pin header with mostly digital signals. The additional NRST (pin3)
/Zephyr-Core-3.5.0/drivers/virtualization/
DKconfig57 This is mostly a module to help getting info the ivshmem and/or
/Zephyr-Core-3.5.0/soc/arm/nxp_lpc/lpc11u6x/
Diap.h11 * code. Mostly they provide access to the on-chip flash and EEPROM devices.
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dnet_timeout.rst13 Zephyr's network infrastructure mostly uses the millisecond-resolution uptime
/Zephyr-Core-3.5.0/drivers/pcie/endpoint/
Dpcie_ep_iproc_msi.c56 * This is mostly the case where the test is being run in iproc_pcie_generate_msi()
89 * This is mostly the case where the test is being run in generate_msix()
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig.stats37 This is meant for testing mostly.
/Zephyr-Core-3.5.0/include/zephyr/net/
Dudp.h24 /* These APIs are mostly meant for Zephyr internal use so do not generate
Dieee802154.h35 * subsystem, the native IEEE 802.15.4 L2 subsystem ("Soft" MAC), a mostly
72 * - a basic, mostly PHY-level driver API to be implemented by all drivers,
/Zephyr-Core-3.5.0/doc/develop/toolchains/
Dcustom_cmake.rst17 toolchain for "generic" use, which mostly means running the C preprocessor
/Zephyr-Core-3.5.0/modules/hal_rpi_pico/
DCMakeLists.txt50 # These contain definitions and implementation used mostly for
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/common/
Dboot.c33 * nested function calls, so this is mostly theoretical. Nonetheless
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/conn/src/
Dtest_connect2.c35 * The thread code is mostly a copy of the peripheral_hr sample device
/Zephyr-Core-3.5.0/arch/arm64/core/
Dreset.c74 reg = 0U; /* Mostly RES0 */ in z_arm64_el3_init()
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/cavs/include/
Dxtensa-cavs-linker.ld425 /* Heap start and end markers. Mostly unused, though newlib likes them */
457 /* This is the "extended manifest" data (mostly versioning stuff)
/Zephyr-Core-3.5.0/subsys/net/lib/sockets/
DKconfig104 This is mostly useful for TLS client side to tell TLS server what is
/Zephyr-Core-3.5.0/doc/services/pm/
Ddevice.rst43 When using this type, device power management is mostly done inside
/Zephyr-Core-3.5.0/soc/arm64/nxp_imx/mimx9/
Dlinker.ld9 /* This is mostly a copy of arch/arm64/scripts/linker.ld with
/Zephyr-Core-3.5.0/subsys/pm/
Dpolicy.c34 * states and this is mostly due to the random nature of the substate value
/Zephyr-Core-3.5.0/include/zephyr/lorawan/
Dlorawan.h280 * be enabled for devices with stable RF conditions (i.e., devices in a mostly
/Zephyr-Core-3.5.0/drivers/pwm/
Dpwm_led_esp32.c156 * The APB_CLK is mostly used in pwm_led_esp32_timer_config()

123