Searched full:begins (Results 1 – 25 of 53) sorted by relevance
123
| /Zephyr-latest/dts/bindings/net/wireless/ |
| D | gpio-radio-coex.yaml | 13 transceiver begins their transmission. This is specified by the
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 32 * The stable states are off, on, and error. The service always begins
71 changes, including when a service begins turning off or enters an error
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.multilevel | 50 where storage for 2nd level interrupt ISRs begins. This is
114 where storage for 3rd level interrupt ISRs begins. This is
|
| /Zephyr-latest/arch/x86/core/ |
| D | cpuhalt.c | 34 * "After the IF flag is set, the processor begins responding to in arch_cpu_atomic_idle()
|
| /Zephyr-latest/dts/bindings/mipi-dsi/ |
| D | renesas,ra-mipi-dsi.yaml | 51 Set the delay value inside DSI Host until the transfer begins.
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | multiboot.h | 56 * Magic numbers: the kernel multiboot header (see crt0.S) begins with
|
| /Zephyr-latest/dts/bindings/mtd/ |
| D | fixed-partitions.yaml | 48 the partition begins at that offset from the parent flash
|
| /Zephyr-latest/include/zephyr/crypto/ |
| D | hash.h | 63 * Hash handler set up when the session begins.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | system_threads.rst | 53 An application-supplied ``main()`` function begins executing once
|
| /Zephyr-latest/drivers/dai/intel/dmic/ |
| D | dmic_nhlt.h | 113 * each value takes one DWORD (32-bits) or in packed form where the array begins with
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 61 The configuration phase begins when the user invokes *CMake* to generate a
70 CMake begins by processing the :file:`CMakeLists.txt` file in the application
137 The build phase begins when the user invokes ``make`` or ``ninja``. Its
170 Compilation proper begins with the first intermediate binary. Source files (C
|
| /Zephyr-latest/arch/x86/core/ia32/ |
| D | thread.c | 113 * doesn't care about their state when execution begins in arch_new_thread()
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/src/ |
| D | main.c | 61 * Work queuing begins when the MQTT connection is established.
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | timers.rst | 53 the **running** state and begins counting down towards expiry.
76 The timer's status is reset to zero, then the timer begins counting down
|
| /Zephyr-latest/doc/develop/west/ |
| D | config.rst | 187 element begins with ``-``. The project is activated if the element
188 begins with ``+``. (Project names cannot contain ``,`` if this option is
|
| /Zephyr-latest/include/zephyr/ |
| D | irq.h | 35 * subsequently enabled before the interrupt handler begins servicing
102 * subsequently enabled via irq_enable() before the interrupt handler begins
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | retained_mem.h | 75 * application begins execution or the device is rebooted (without power loss). It must support
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | thread.c | 106 * begins the C function. And A4-A7 and A8-A11 are optional in init_stack()
|
| /Zephyr-latest/soc/silabs/silabs_siwx91x/ |
| D | siwx91x_isp_prepare.py | 144 help="Address at which the raw binary image begins in the memory",
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | mutexes.rst | 67 if a higher priority thread begins waiting on the mutex. This allows the owning
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 49 Offset that the kernel image begins within its address space,
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 177 the address where the region begins.
182 CONFIG_SRAM_BASE_ADDRESS to determine the address where the region begins.
|
| /Zephyr-latest/subsys/dfu/img_util/ |
| D | flash_img.c | 229 * the firmware update process begins in flash_img_init_id()
|
| /Zephyr-latest/modules/thrift/src/thrift/server/ |
| D | TServer.h | 62 * Called before the server begins.
|
| /Zephyr-latest/scripts/logging/dictionary/dictionary_parser/ |
| D | log_parser_v1.py | 315 # the offset begins at 0 for va_list. However, the format string
|
123
