Searched refs:boundary (Results 1 – 25 of 49) sorted by relevance
12
| /Zephyr-latest/drivers/disk/nvme/ |
| D | nvme_namespace.c | 75 return ns->boundary; in nvme_namespace_get_stripesize()
117 ns->boundary = ns->data.noiob * nvme_namespace_get_sector_size(ns); in nvme_namespace_construct()
|
| D | nvme_namespace.h | 166 uint32_t boundary; member
|
| /Zephyr-latest/subsys/fb/ |
| D | cfb_shell.c | 194 int boundary; in cmd_scroll_vert() local
208 boundary = cfb_get_display_parameter(dev, CFB_DISPLAY_ROWS) - row; in cmd_scroll_vert()
210 for (int i = 0; i < boundary; i++) { in cmd_scroll_vert()
230 int boundary; in cmd_scroll_horz() local
245 boundary = cfb_get_display_parameter(dev, CFB_DISPLAY_COLS) - col; in cmd_scroll_horz()
247 for (int i = 0; i < boundary; i++) { in cmd_scroll_horz()
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_k8xfn256vxx15.dtsi | 13 * across the 0x2000_0000 boundary are not supported in the Arm
|
| D | nxp_ke1xf256vlx16.dtsi | 13 * across the 0x2000_0000 boundary are not supported in the Arm
|
| D | nxp_ke1xf512vlx16.dtsi | 13 * across the 0x2000_0000 boundary are not supported in the Arm
|
| D | nxp_s32k146.dtsi | 20 * and burst accesses cannot occur across the 0x20000000 boundary
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | slabs.rst | 33 The memory slab's buffer must be aligned to an N-byte boundary, where
35 all memory blocks in the buffer are similarly aligned to this boundary,
74 that are 400 bytes long, each of which is aligned to a 4-byte boundary.
|
| D | sys_mem_blocks.rst | 43 The buffer must be aligned to an N-byte boundary, where N is a power of 2
45 the buffer are similarly aligned to this boundary, the block size must
109 to a 4-byte boundary:
|
| /Zephyr-latest/lib/net_buf/ |
| D | Kconfig | 58 to a certain byte boundary, or dealing with cache line restrictions.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 18 NS/S boundary via the PSA APIs. They provide a useful sanity check for proper
|
| /Zephyr-latest/include/zephyr/linker/common-rom/ |
| D | common-rom-init.ld | 9 * boundary. To align with the C++ standard, the first element
|
| D | common-rom-kernel-devices.ld | 53 * specific boundary for using double word load
|
| /Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/tippy/ |
| D | popper.min.js | 7 …boundary,c=void 0===f?"clippingParents":f,u=r.rootBoundary,l=void 0===u?H:u,h=r.elementContext,m=v…
|
| /Zephyr-latest/arch/x86/ |
| D | ia32.cmake | 7 zephyr_cc_option(-mpreferred-stack-boundary=2)
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | common-ram.ld | 24 * specific boundary for using double word load
|
| /Zephyr-latest/include/zephyr/arch/sparc/ |
| D | linker.ld | 142 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_stack_objects.rst | 48 This means that a 1500 byte stack should be aligned to a 2kB boundary and the
|
| /Zephyr-latest/boards/nxp/frdm_rw612/ |
| D | frdm_rw612_common.dtsi | 61 ahb-boundary = "1024";
|
| /Zephyr-latest/samples/subsys/display/cfb_shell/ |
| D | README.rst | 123 until it hits the display boundary, last column for horizontal and last row
|
| /Zephyr-latest/include/zephyr/arch/mips/ |
| D | linker.ld | 169 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
| /Zephyr-latest/soc/infineon/cat1b/cyw20829/ |
| D | linker.ld | 285 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
354 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
| /Zephyr-latest/include/zephyr/arch/arm/cortex_m/scripts/ |
| D | linker.ld | 302 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
474 * section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | stacks.rst | 24 and must be aligned on a native word boundary.
|
| /Zephyr-latest/soc/cdns/xtensa_sample_controller/include/ |
| D | xtensa-sample-controller.ld | 90 /* Memory boundary addresses: */
102 /* Memory segment boundary addresses: */
|
12
