Searched full:initialization (Results 1 – 25 of 1143) sorted by relevance
12345678910>>...46
14 * zephyr architecture and initialization code and the SoC and board specific logic27 * SoC-specific initialization.35 * SoC-specific initialization.43 * SoC-specific initialization.51 * SoC-specific initialization.56 * @brief SoC per-core initialization59 * SoC-specific per-core initialization68 * initialization.77 * any board-specific initialization.
21 * @defgroup sys_init System Initialization24 * Zephyr offers an infrastructure to call initialization code before `main`.25 * Such initialization calls can be registered using SYS_INIT() or26 * SYS_INIT_NAMED() macros. By using a combination of initialization levels and28 * initialization levels are described, in order, below:34 * specific initialization code.35 * - `PRE_KERNEL_1`: Executed in Kernel's initialization context, which uses44 * Initialization priority can take a value in the range of 0 to 99.53 * @brief Structure to store initialization entry information.69 * initialization function, otherwise it is set to NULL.[all …]
38 menu "Initialization Priorities"41 int "Kernel objects initialization priority"44 Kernel objects use this priority for initialization. This45 priority needs to be higher than minimal default initialization49 int "LIBC initialization priority"52 LIBC uses this priority for initialization. This53 priority needs to be higher than minimal default initialization
28 Run an early SoC initialization hook.36 Run a late SoC initialization hook.42 bool "Run SoC per-core initialization hook"44 Run an SoC initialization hook for every core53 Run an early board initialization hook.61 Run a late board initialization hook.
21 NCT38xx GPIO driver initialization priority. The priority must be lower28 NCT38xx GPIO port device driver initialization priority. The priority43 NCT38XX alert handler initialization priority. This initialization
14 int "nPM6001 GPIO driver initialization priority"18 Initialization priority for the nPM6001 GPIO driver.
19 Power domain initialization priority.36 GPIO power domain initialization priority.54 Intel ADSP power domain initialization priority.72 GPIO monitor power domain initialization priority.89 NXP SCU-managed PD driver initialization priority.
7 int "Board initialization priority"12 Board initialization priority. The board initialization must take
22 System clock source initialization waits until clock is available. In some26 system clock driver initialization but it may be less accurate. Option is33 System clock source initialization waits until clock is stable. When this35 driver initialization.
46 int "SCMI shared memory (SHMEM) initialization priority"49 SCMI SHMEM driver device initialization priority.62 int "SCMI transport layer initialization priority"65 SCMI transport driver device initialization priority.
19 - "eSPI test - I/O initialization...complete"21 - "eSPI test - callbacks initialization... complete"22 - "eSPI test - Power initialization...complete"26 - "espi: eSPI test - callbacks initialization..."
6 after initialization, as most registers present on the card will be vendor11 test the initialization flow of the SDIO subsystem to verify that the stack18 for this card after initialization.
114 prompt "RTT Initialization mode"116 RTT initialization function can avoid re-init of Control Block122 bool "RTT Initialization done without conditions"125 bool "RTT Initialization done if full check on Control Block ID fails"128 bool "RTT Initialization done if partial check on Control Block ID fails"
39 types during driver pre-initialization.46 types during driver pre-initialization.53 types during driver pre-initialization.
10 /* Initialization chain of Thingy:53 board requires some delays before on board sensors13 * introduced in the board start up file. Below asserts ensure correct initialization order:35 /* Initialization chain of Thingy:53 board requires some delays before on board in setup()39 * executed after sensors are powered up and before their initialization. in setup()
20 in those chips and at initialization configures them to work in34 int "Driver initialization priority"37 Device driver initialization priority.
22 int "CC2520 initialization priority"25 Set the initialization priority number. Do not mess with it unless78 int "TI CC2520 crypto device initialization priority"82 Set the initialization priority number. Do not mess with it unless
15 int "Initialization priority"18 ILI9806E_DSI display driver initialization priority.
15 int "Initialization priority"18 OTM8009A display driver initialization priority.
15 int "Initialization priority"18 NT35510 display driver initialization priority.
14 int "nPM6001 Watchdog driver initialization priority"18 Initialization priority for the nPM6001 Watchdog driver.
7 int "Remap routine initialization priority"10 Initialization priority of the remap routine within the PRE_KERNEL1 level.
12 int "RV32M1 initialization priority"16 RV32M1 pin controller initialization priority.
9 * @brief Full C support initialization12 * Initialization of full C support: zero the .bss and call z_cstart().15 * initialization is performed.
34 /** initialization function */39 * @defgroup LWM2M_PRIO LwM2M initialization priorities42 #define LWM2M_PRIO_ENGINE 0 /**< Engine initialization */43 #define LWM2M_PRIO_CORE 1 /**< Core object initialization */45 #define LwM2M_PRIO_APP 3 /**< Application logic initialization */49 * @brief Declare an initialization function to be executed when LwM2M engine starts.51 * When LwM2M engine starts up, it first executes all initialization functions in following56 * 4. LwM2M_PRIO_APP, application initialization.60 * @param[in] init_function Initialization function67 * @brief Declare engine initialization function.[all …]
