/Zephyr-latest/drivers/spi/ |
D | spi_mcux_ecspi.c | 191 master_config.channelConfig.phase = in spi_mcux_configure()
|
D | spi_mcux_flexcomm.c | 232 master_config.phase = in spi_mcux_configure() 273 slave_config.phase = in spi_mcux_configure()
|
/Zephyr-latest/cmake/linker/armlink/ |
D | target.cmake | 108 # deprecated there. For current ARMClang support phase, we accept this warning, but we should
|
/Zephyr-latest/doc/releases/ |
D | migration-guide-3.5.rst | 418 * ``phase-seg1`` 419 * ``phase-seg1`` 422 * ``phase-seg1-data`` 423 * ``phase-seg1-data``
|
D | migration-guide-3.7.rst | 293 * ``phase-seg1`` 294 * ``phase-seg2`` 297 * ``phase-seg1-data`` 298 * ``phase-seg2-data``
|
/Zephyr-latest/doc/services/llext/ |
D | config.rst | 80 phase. Once the extension is unloaded, the buffer must be reloaded
|
/Zephyr-latest/drivers/disk/nvme/ |
D | nvme_cmd.h | 332 uint32_t phase; member
|
/Zephyr-latest/subsys/bluetooth/mesh/shell/ |
D | cfg.c | 1455 uint8_t status, phase; in cmd_krp() local 1468 &phase); in cmd_krp() 1479 &phase); in cmd_krp() 1488 phase); in cmd_krp()
|
D | dfu.c | 599 shell_print(sh, "\tPhase: %u", rsp.phase); in cmd_dfu_target_state() 600 if (rsp.phase != BT_MESH_DFU_PHASE_IDLE) { in cmd_dfu_target_state()
|
D | blob.c | 154 target->addr, info->phase, progress); in xfer_progress()
|
/Zephyr-latest/samples/bluetooth/channel_sounding/ |
D | README.rst | 28 which is enough to estimate distance using a handful of RTT timings and PBR phase samples across
|
/Zephyr-latest/tests/bluetooth/tester/src/btp/ |
D | btp_mesh.h | 743 uint8_t phase; member 755 uint8_t phase; member
|
/Zephyr-latest/boards/renesas/mck_ra8t1/doc/ |
D | index.rst | 154 …ci-lv-1-renesas-flexible-motor-control-inverter-board-low-voltage-48v10a-three-phase-bldcpmsm-motor
|
/Zephyr-latest/samples/net/gptp/ |
D | README.rst | 11 gPTP phase discontinuity callback, enable traffic class support (TX multi
|
/Zephyr-latest/subsys/testsuite/ztest/src/ |
D | ztest.c | 371 static inline const char *get_friendly_phase_name(enum ztest_phase phase) in get_friendly_phase_name() argument 373 switch (phase) { in get_friendly_phase_name()
|
/Zephyr-latest/dts/arm/raspberrypi/rpi_pico/ |
D | rp2040.dtsi | 156 phase = <0>;
|
D | rp2350.dtsi | 152 phase = <0>;
|
/Zephyr-latest/tests/bluetooth/tester/src/ |
D | btp_mesh.c | 2313 uint8_t phase; in config_krp_get() local 2321 &status, &phase); in config_krp_get() 2329 rp->phase = phase; in config_krp_get() 2342 uint8_t phase; in config_krp_set() local 2350 cp->transition, &status, &phase); in config_krp_set() 2357 rp->phase = phase; in config_krp_set()
|
/Zephyr-latest/doc/hardware/arch/ |
D | arm-scmi.rst | 124 …#. Zephyr rings request doorbell. If in ``PRE_KERNEL_1`` or ``PRE_KERNEL_2`` phase start polling f…
|
/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/tippy/ |
D | tippy-bundle.umd.min.js | 6 …phase:"beforeWrite",requires:["computeStyles"],fn:function(t){var e=t.state;if(tt()){var n=rt().bo… property in AnonymousFunction026bd4794700.a
|
/Zephyr-latest/doc/develop/api/ |
D | api_lifecycle.rst | 257 In this phase, the API is removed.
|
/Zephyr-latest/doc/services/tfm/ |
D | overview.rst | 236 material is never exposed, or even known during the provisioning phase.
|
/Zephyr-latest/doc/security/ |
D | secure-coding.rst | 126 validation phase. In each stage, appropriate documentation shall be
|
/Zephyr-latest/doc/build/dts/ |
D | troubleshooting.rst | 21 issues, because the outputs are created during the CMake configuration phase,
|
/Zephyr-latest/doc/contribute/ |
D | bin_blobs.rst | 90 - The Zephyr build system, during its configuration phase, will issue a warning.
|