Searched full:stages (Results 1 – 25 of 35) sorted by relevance
12
| /Zephyr-latest/dts/bindings/clock/ |
| D | raspberrypi,pico-rosc.yaml | 16 Specify the number of ring oscillator stages to use.
26 Specifies the drive strength of the eight stages of the ring oscillator.
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | kobject-rom.ld | 11 * produced by gperf during the final stages of linking.
15 * during the final stages of linking (LINKER_ZEPHYR_FINAL).
|
| D | kobject-priv-stacks.ld | 15 * produced by gperf during the final stages of linking.
19 * during the final stages of linking (LINKER_ZEPHYR_FINAL).
|
| D | kobject-data.ld | 25 * produced by gperf during the final stages of linking.
29 * during the final stages of linking (LINKER_ZEPHYR_FINAL).
|
| /Zephyr-latest/dts/bindings/i2c/ |
| D | renesas,rz-riic.yaml | 37 noise-filter-stages:
|
| /Zephyr-latest/soc/nordic/ |
| D | Kconfig | 138 at later stages, for example, to implement authenticated debug.
180 handle it at later stages, for example, to implement authenticated
|
| /Zephyr-latest/cmake/toolchain/arcmwdt/ |
| D | generic.cmake | 32 # For other build stages ARCMWDT will be used.
|
| /Zephyr-latest/drivers/pinctrl/ |
| D | Kconfig | 34 peripheral at early boot stages depending on a certain input.
|
| /Zephyr-latest/include/zephyr/linker/common-rom/ |
| D | common-rom-kernel-devices.ld | 32 * the linking stages will end up shifting the addresses of the
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 7 early boot stages, depending on the input level on a pin connected to a
|
| /Zephyr-latest/tests/lib/cmsis_dsp/filtering/src/ |
| D | biquad_f16.c | 39 coeff_mod = calloc(47, sizeof(arm_biquad_mod_coef_f16)); /* 47 stages */ in ZTEST()
151 coeff_mod = calloc(47, sizeof(arm_biquad_mod_coef_f16)); /* 47 stages */ in ZTEST()
|
| D | biquad_f32.c | 38 coeff_mod = calloc(47, sizeof(arm_biquad_mod_coef_f32)); /* 47 stages */ in ZTEST()
148 coeff_mod = calloc(47, sizeof(arm_biquad_mod_coef_f32)); /* 47 stages */ in ZTEST()
|
| /Zephyr-latest/scripts/build/ |
| D | gen_kobject_placeholders.py | 14 the same during later stages of linking.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 76 Stages subsection
79 The Bluetooth Mesh DFU process is designed to act in three stages:
244 :alt: Overview of DFU stages and procedures
246 DFU stages and procedures as seen from the Distributor
|
| /Zephyr-latest/drivers/net/ |
| D | loopback.c | 126 * the packet is reference counted in various stages of sending. in loopback_send()
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | ring_buffers.rst | 125 directly by the user. In the latter case, the operation is split into three stages:
136 case, the operation is split into three stages:
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 153 are the agreed upon stages:
171 stages, refine/iterate on selected rules.
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | sync_rtc.c | 42 * consists of two stages: Getting offset on APP side, passing this offset to
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 8 CMake build is done in two stages. The first stage is called
141 into four stages: the pre-build, first-pass binary, final binary, and
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 422 - **Lifecycle management:** system stages shall be defined and
423 documented along with the transactions between the stages in a
452 modules in all of its stages and the management of reported security
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_testinstance.py | 196 stages = TwisterRunner.get_cmake_filter_stages(filter_expr, logic_keys)
197 assert sorted(stages) == sorted(expected_stages)
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 196 There are two stages required to support conversion between Zephyr time and
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 13 # various build stages, as well as to other arbitrary Python scripts:
|
| /Zephyr-latest/drivers/dai/nxp/esai/ |
| D | esai.h | 168 * during the same stages as PRRC.
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 44 # Zephyr build system will use a dynamic number of linking stages based on build
47 # Currently up to three linking stages may be executed:
56 # Multiple linking stages are required in the following cases:
65 # When all three linking stages are active, then the following properties applies:
|
12
