Home
last modified time | relevance | path

Searched full:space (Results 1 – 25 of 837) sorted by relevance

12345678910>>...34

/Zephyr-Core-3.6.0/samples/modules/tflite-micro/magic_wand/renode/
Dlitex-vexriscv-tflite.robot24 Wait For Line On Uart ${SPACE*10}*
25 Wait For Line On Uart ${SPACE*7}*${SPACE*5}*
26 Wait For Line On Uart ${SPACE*5}*${SPACE*9}*
27 Wait For Line On Uart ${SPACE*4}*${SPACE*11}*
28 Wait For Line On Uart ${SPACE*5}*${SPACE*9}*
29 Wait For Line On Uart ${SPACE*7}*${SPACE*5}*
30 Wait For Line On Uart ${SPACE*10}*
44 Wait For Line On Uart ${SPACE*8}*
45 Wait For Line On Uart ${SPACE*7}*
46 Wait For Line On Uart ${SPACE*6}*
[all …]
/Zephyr-Core-3.6.0/doc/hardware/arch/
Dx86.rst16 is executing in virtual address space. By default, physical and virtual
18 taking place in physical address space. The physical address space is
20 :kconfig:option:`CONFIG_SRAM_SIZE` while the virtual address space is marked by
26 Separate Virtual Address Space from Physical Address Space
30 address space. Code and data are linked in virtual address space,
33 space before ``vm_enter`` inside :file:`arch/x86/core/ia32/crt0.S`.
46 additional space for the page table. However, additional space may
49 There are restrictions on where virtual address space can be:
56 - If :kconfig:option:`CONFIG_X86_PAE` is enabled (``=y``), each address space
69 - If :kconfig:option:`CONFIG_X86_PAE` is disabled (``=n``), each address space
[all …]
/Zephyr-Core-3.6.0/
D.editorconfig36 indent_style = space
46 indent_style = space
51 indent_style = space
56 indent_style = space
67 indent_style = space
72 indent_style = space
D.clang-format5 # git grep -h '^#define [^[:space:]]*FOR_EACH[^[:space:]]*(' include/ \
6 # | sed "s,^#define \([^[:space:]]*FOR_EACH[^[:space:]]*\)(.*$, - '\1'," \
/Zephyr-Core-3.6.0/drivers/xen/
Dmemory.c14 unsigned int space, xen_pfn_t gpfn) in xendom_add_to_physmap() argument
19 .space = space, in xendom_add_to_physmap()
27 unsigned int space, unsigned int size, in xendom_add_to_physmap_batch() argument
33 .space = space, in xendom_add_to_physmap_batch()
/Zephyr-Core-3.6.0/include/zephyr/xen/
Dmemory.h15 * @param idx index into space being mapped.
16 * @param space XENMAPSPACE_* mapping space identifier.
20 int xendom_add_to_physmap(int domid, unsigned long idx, unsigned int space,
30 * @param space XENMAPSPACE_* mapping space identifier.
32 * @param idxs array of indexes into space being mapped.
38 unsigned int space, unsigned int size,
/Zephyr-Core-3.6.0/boards/arm/scobc_module1/
DKconfig.board1 # Space Cubics OBC module 1 configuration
3 # Copyright (c) 2021 Space Cubics, LLC. <yashi@spacecubics.com>
7 bool "Space Cubics OBC Module 1"
DKconfig.defconfig1 # Space Cubics OBC module 1
3 # Copyright (c) 2021 Space Cubics <yashi@spacecubics.com>
/Zephyr-Core-3.6.0/tests/subsys/logging/log_core_additional/src/
Dlog_test_user.c22 /* Interfaces tested in these cases have been tested in kernel space.
23 * Test cases in this file run in user space to improve test coverage
40 /* test log_hexdump_from_user() from user space */
59 /* test log_generic() from user space */
69 /* test log_filter_set from user space */
75 /* test log_panic() from user space */
/Zephyr-Core-3.6.0/include/zephyr/drivers/pcie/
Dcontroller.h34 * @brief Function called to read a 32-bit word from an endpoint's configuration space.
36 * Read a 32-bit word from an endpoint's configuration space with the PCI Express Controller
37 * configuration space access method (I/O port, memory mapped or custom method)
48 * @brief Function called to write a 32-bit word to an endpoint's configuration space.
50 * Write a 32-bit word to an endpoint's configuration space with the PCI Express Controller
51 * configuration space access method (I/O port, memory mapped or custom method)
68 * such region is available and space is still available.
130 * @brief Read a 32-bit word from a Memory-Mapped endpoint's configuration space.
132 * Read a 32-bit word from an endpoint's configuration space from a Memory-Mapped
133 * configuration space access method, known as PCI Control Access Method (CAM) or
[all …]
/Zephyr-Core-3.6.0/kernel/
DKconfig.vm17 hex "Virtual address space base address"
20 Define the base of the kernel's address space.
35 the kernel's address space, such as not overlapping physical RAM
41 Zephyr does not implement a split address space and if multiple
46 hex "Kernel offset within address space"
49 Offset that the kernel image begins within its address space,
66 hex "Size of kernel address space in bytes"
69 Size of the kernel's address space. Constraining this helps control
81 RAM size larger than the defined bounds of the virtual address space.
90 If the specific memory region is in the virtual memory space and
[all …]
/Zephyr-Core-3.6.0/doc/kernel/drivers/
Ddevice_driver_model.svg3space: nowrap; overflow-wrap: normal; text-align: left;"><div xmlns="http://www.w3.org/1999/xhtml"…
/Zephyr-Core-3.6.0/doc/kernel/memory_management/
Dvirtual_memory.rst29 * Although the virtual memory space can be larger than physical
30 memory space, without enabling demand paging, all virtually
48 * :kconfig:option:`CONFIG_KERNEL_VM_BASE`: base address of virtual address space.
50 * :kconfig:option:`CONFIG_KERNEL_VM_SIZE`: size of virtual address space.
61 the virtual address space. This is useful for mapping device MMIO regions for
68 This is an overview of the memory map of the virtual memory address space.
101 * ``Z_VIRT_RAM_START`` is the beginning of the virtual memory address space.
105 * ``Z_VIRT_RAM_SIZE`` is the size of the virtual memory address space.
118 * ``Z_FREE_VM_START`` is the beginning of the virtual address space where addresses
123 memory address space, and it is the same as
[all …]
/Zephyr-Core-3.6.0/doc/kernel/data_structures/
Dmpsc_pbuf.rst21 * Following policies can be applied when requested space cannot be allocated:
25 * **No overwrite** - When requested amount of space cannot be allocated,
47 | 0 | 0 | space is free |
56 Packet buffer space contains free space, valid user packets and internal skip
62 Using pairs for read and write indexes, available space is determined. If
63 space can be allocated, temporary write index is moved and pointer to a space
66 space cannot be allocated and overwrite is disabled then ``NULL`` pointer is
73 space can be allocated. When packets are dropped ``busy`` flag is checked in the
/Zephyr-Core-3.6.0/doc/services/storage/fcb/
Dfcb.rst23 request space for the next entry, space is located at the end of the
27 Entries can be appended to the end of the area until storage space is
29 block of data, thereby freeing up some space, or stop writing new data
44 this fails due to lack of space, you can call :c:func:`fcb_rotate` to erase
45 the oldest sector which will make the space. And then call
/Zephyr-Core-3.6.0/doc/services/portability/posix/overview/
Dposix.svg2space: nowrap; overflow-wrap: normal; text-align: center;"><div xmlns="http://www.w3.org/1999/xhtm…
/Zephyr-Core-3.6.0/dts/bindings/ipm/
Dxlnx,zynqmp-ipi-mailbox.yaml16 description: IPI control and status register space
33 description: register space for IPI message buffers
38 description: name of each register space
/Zephyr-Core-3.6.0/subsys/logging/backends/
DKconfig.rtt13 is transferred to up-buffer at once depending on available space and
15 In panic mode backend always blocks and waits until there is space
27 If there is not enough space in up-buffer for a message, drop it.
34 Waits until there is enough space in the up-buffer for a message.
39 If there is not enough space in up-buffer for a message overwrite
/Zephyr-Core-3.6.0/scripts/dts/python-devicetree/tests/test-wrong-bindings/
Dwrong-specifier-space-type.yaml8 wrong-type-for-specifier-space:
10 specifier-space: foobar
/Zephyr-Core-3.6.0/doc/build/dts/
Dphandles.rst227 Every phandle-array property has an associated *specifier space*. This sounds
229 follow each phandle in a hardware specific way. Every specifier space has a
235 ``phandle-array-prop``\ 's specifier space is named ``baz``. Then we would need
266 With that, if ``phandle-array-prop-2`` has specifier space ``bob``, we could
281 Example specifier space: gpio
284 From the above example, you're already familiar with how one specifier space
285 works: in the "gpio" space, specifiers almost always have two cells:
305 - each phandle-array property has an associated specifier space
317 specifier space ``foo``. For example:
327 The ``dmas`` property's specifier space is "dma". The ``pwm`` property's
[all …]
/Zephyr-Core-3.6.0/boards/arm/mimx8mp_phyboard_pollux/
Dmimx8mp_phyboard_pollux_defconfig17 # y for TCM memory space
20 # y for DDR memory space
/Zephyr-Core-3.6.0/boards/arm/scobc_module1/doc/
Dindex.rst3 Space Cubics OBC module 1
9 `Space Cubics`_ OBC module 1 is a single board computer for spacecraft,
15 :alt: Space Cubics OBC module 1
17 Space Cubics OBC module 1
19 It is designed to survive in the severe space environment, extreme temperature,
20 vacuum, and space radiation.
33 The Space Cubics OBC module 1 provides the following hardware features:
/Zephyr-Core-3.6.0/dts/bindings/pcie/endpoint/
Dbrcm,iproc-pcie-ep.yaml14 Register space for the memory mapped PAX(PCIe to AXI bridge) registers,
15 It includes registers to access EP configuration space
/Zephyr-Core-3.6.0/include/zephyr/linker/
Dkobject-rom.ld10 * space needs to be reserved for the rodata that will be
46 "scripts/build/gen_kobject_placeholders.py did not reserve enough space \
51 * if we have reserved more space than needed.
Dkobject-priv-stacks.ld14 * space needs to be reserved for the rodata that will be
45 "scripts/build/gen_kobject_placeholders.py did not reserve enough space \
50 * if we have reserved more space than needed.

12345678910>>...34