Searched full:varies (Results 1 – 22 of 22) sorted by relevance
| /Zephyr-Core-3.6.0/samples/subsys/display/lvgl/ |
| D | sample.yaml | 7 # flash usage varies depending on the platform, but ~200K are the bare
|
| /Zephyr-Core-3.6.0/tests/subsys/logging/log_immediate/src/ |
| D | log_immediate_test.c | 35 * (data length varies for each thread) and sleeps. Threads have different
|
| /Zephyr-Core-3.6.0/include/zephyr/arch/x86/ |
| D | thread_stack.h | 39 * | Thread stack (varies) |
|
| /Zephyr-Core-3.6.0/include/zephyr/arch/arm/cortex_m/ |
| D | memory_map.h | 48 /* 0xe0000000 -> 0xffffffff: varies by processor (see below) */
|
| /Zephyr-Core-3.6.0/dts/bindings/mtd/ |
| D | atmel,sam-flash.yaml | 7 The Atmel SAM flash area varies in write-block-size, memory area,
|
| /Zephyr-Core-3.6.0/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 55 As this information varies with every use case, it is difficult to come up
|
| /Zephyr-Core-3.6.0/doc/develop/languages/c/ |
| D | index.rst | 95 While the details of the dynamic memory management implementation varies across
|
| /Zephyr-Core-3.6.0/include/zephyr/lorawan/ |
| D | lorawan.h | 253 * buffer is 255 bytes but the actual payload size varies with
320 * Query the current payload sizes. The maximum payload size varies with
|
| /Zephyr-Core-3.6.0/include/zephyr/app_memory/ |
| D | mem_domain.h | 143 * varies per architecture.
|
| /Zephyr-Core-3.6.0/kernel/ |
| D | Kconfig.vm | 114 Size of memory pages. Varies per MMU but 4K is common. For MMUs that
|
| /Zephyr-Core-3.6.0/dts/bindings/clock/ |
| D | nuvoton,npcx-pcc.yaml | 216 varies in different NPCX series.
|
| /Zephyr-Core-3.6.0/doc/kernel/usermode/ |
| D | overview.rst | 169 varies per architecture.
|
| /Zephyr-Core-3.6.0/include/zephyr/sys/ |
| D | device_mmio.h | 205 * What gets stored here varies considerably by configuration.
392 * What gets stored here varies considerably by configuration. Multiple named
|
| /Zephyr-Core-3.6.0/doc/kernel/ |
| D | timeutil.rst | 142 changes in Earth’s rotation. Thus the difference between TAI and UT varies
|
| /Zephyr-Core-3.6.0/doc/services/tracing/ |
| D | index.rst | 29 In fact, I/O varies greatly from system to system. Therefore, it is
|
| /Zephyr-Core-3.6.0/arch/arm/core/mpu/ |
| D | nxp_mpu.c | 401 * varies depending on the SOC. Each descriptor has a start addr, end in mpu_configure_dynamic_mpu_regions()
|
| /Zephyr-Core-3.6.0/arch/x86/ |
| D | gen_mmu.py | 226 """Number of entries in the table. Varies by table type and paging
|
| /Zephyr-Core-3.6.0/doc/connectivity/usb/device/ |
| D | usb_device.rst | 98 Since the designation of the controller nodes varies from vendor to vendor,
|
| /Zephyr-Core-3.6.0/doc/services/logging/ |
| D | index.rst | 820 also significantly varies between platforms. In general, when :kconfig:option:`CONFIG_LOG_MODE_DEFE…
|
| /Zephyr-Core-3.6.0/include/zephyr/drivers/ |
| D | sensor.h | 222 * Trigger fires when the selected channel varies significantly.
|
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/ |
| D | gatt.h | 1653 * callback varies depending on the type of read operation.
|
| /Zephyr-Core-3.6.0/include/zephyr/net/ |
| D | ieee802154_radio.h | 885 * slot accordingly. If the driver finds that the offset varies from
|
