Searched refs:early (Results 1 – 25 of 57) sorted by relevance
123
| /Zephyr-latest/kernel/ |
| D | Kconfig.init | 10 bool "Run early SoC reset hook"
12 Run an early SoC reset hook.
18 bool "Run early SoC preparation hook"
20 Run an early SoC preparation hook.
26 bool "Run early SoC hook"
28 Run an early SoC initialization hook.
51 bool "Run early board hook"
53 Run an early board initialization hook.
|
| D | Kconfig.vm | 32 instruction pointer to virtual addresses at early boot before
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_grtc | 49 too early. In other words, applying SYSCOUNTER sleep state for less than
|
| /Zephyr-latest/lib/utils/ |
| D | Kconfig | 48 The sys_winstream utility is sometimes used in early boot
|
| /Zephyr-latest/cmake/toolchain/arcmwdt/ |
| D | generic.cmake | 27 # On very early stage build system needs to get access to DTC preprocessor.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 15 During very early boot, page tables are loaded so technically the kernel
84 access during very early boot. To pass extra command line arguments to
|
| /Zephyr-latest/drivers/pinctrl/ |
| D | Kconfig | 34 peripheral at early boot stages depending on a certain input.
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.intel64 | 28 processing and early kernel/CPU initialization. They need only
|
| /Zephyr-latest/soc/atmel/sam0/common/ |
| D | Kconfig.saml2x | 11 These can be mitigated by inserting a small delay during the early boot
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 60 int "Buffer size to store early messages"
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | lwm2m_rd_client.c | 1117 int64_t early = CONFIG_LWM2M_SECONDS_TO_UPDATE_EARLY; in next_update() local
1122 if (early > client.lifetime) { in next_update()
1123 early = client.lifetime; in next_update()
1126 next = MIN(period, client.lifetime - early); in next_update()
|
| /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/subsys/net/l2/wifi/ |
| D | Kconfig | 36 If TWT setup is triggered early in the connection, then device might
|
| /Zephyr-latest/subsys/random/ |
| D | Kconfig | 36 early random number genenator.
|
| /Zephyr-latest/modules/hostap/ |
| D | Kconfig | 575 bool "Exit early if PWE if found"
579 this can be intensive, so, add an option to exit early.
|
| /Zephyr-latest/arch/arc/ |
| D | Kconfig | 386 bool "Make early stage SoC-specific initialization"
388 Call SoC per-core setup code on early stage initialization
|
| /Zephyr-latest/boards/xen/xenvm/doc/ |
| D | index.rst | 91 * Xen early console_io interface (mainly for debug purposes - requires debug version of Xen)
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig | 78 early in the flow after the VW channel is configured. Or it could be
|
| /Zephyr-latest/boards/adi/max32655fthr/doc/ |
| D | index.rst | 13 early software development to enhance time to market. Go to
|
| /Zephyr-latest/boards/adi/max32672fthr/doc/ |
| D | index.rst | 10 a power-optimized flexible platform for quick proof-ofconcepts and early software development
|
| /Zephyr-latest/boards/blues/swan_r5/doc/ |
| D | index.rst | 13 developers' needs that span from early prototyping through high-volume
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 135 offer early prototypes of features before they become
163 infrastructure that provides coverage baselines, catches issues early,
|
| /Zephyr-latest/doc/kernel/ |
| D | code-relocation.rst | 147 Take care if relocating kernel/arch files, some contain early initialization
|
| /Zephyr-latest/boards/adi/max32666fthr/doc/ |
| D | index.rst | 11 This platform provides poweroptimized flexible for quick proof-of-concepts and early software
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 43 programmed into the device, early in production [th-imboot]_.
145 code initially run. This section shall be written early in the
|
123
