Home
last modified time | relevance | path

Searched full:placed (Results 1 – 25 of 316) sorted by relevance

12345678910>>...13

/Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/
DKconfig48 variable if placed on the stack or the maximum allocated size of the
49 variable if placed on the heap.
56 variable if placed on the stack or the allocated size of the
57 variable if placed on the heap (settings does not support getting
/Zephyr-latest/samples/bluetooth/central_hr/
Doverlay-extended.conf3 # Increase Scan Data Length, as Complete Local Name is placed in the
4 # AUX_ADV_IND PDU compared to when it is placed in ADV_SCAN_IND PDU in the case
Doverlay-phy_coded.conf9 # Increase Scan Data Length, as Complete Local Name is placed in the
10 # AUX_ADV_IND PDU compared to when it is placed in ADV_SCAN_IND PDU in the case
/Zephyr-latest/samples/bluetooth/peripheral_hr/
Doverlay-extended.conf4 # placed in the AUX_ADV_IND PDU compared to when it is placed in ADV_SCAN_IND
Doverlay-phy_coded.conf10 # placed in the AUX_ADV_IND PDU compared to when it is placed in ADV_SCAN_IND
/Zephyr-latest/boards/segger/ip_k66f/
Dlinker.ld21 * placed on the index (position) 1 (as net_if_get_by_index() uses
24 * lan{123} shall be placed afterwards (sorted) so the order will be
27 * If ip_k66f have had eth1 interface - it shall be placed afterwards
/Zephyr-latest/tests/application_development/code_relocation/src/
Dtest_file1.c14 * These values will typically be placed in the appropriate sections, but may be moved around
71 /* Print values which were placed using attributes */ in ZTEST()
72 printk("Address of custom_section, func placed using attributes %p\n", in ZTEST()
74 printk("Address of custom_section data placed using attributes %p\n\n", in ZTEST()
/Zephyr-latest/include/zephyr/linker/
Dlinker-devnull.h43 * enough to fit the devnull region then devnull region is placed just after
44 * the ROM region. If it cannot be done then the devnull region is placed before
45 * the ROM region. It is possible that the devnull region cannot be placed
Dirq-vector-table-section.ld9 * Some ARM platforms require this symbol to be placed after the IRQ vector
/Zephyr-latest/boards/nordic/nrf52840dongle/
Dfstab-stock.dtsi15 /* MCUboot placed after Nordic MBR (this is set with the FLASH_LOAD_OFFSET
17 * will be placed at 0x0. The size of this partition ensures that MCUBoot can
/Zephyr-latest/arch/riscv/core/
Dsemihost.c14 * interpret the trap sequence if these instructions are placed across two
19 * never placed across two different pages.
/Zephyr-latest/include/zephyr/sys/
Dlibc-hooks.h85 /* - All newlib globals will be placed into z_libc_partition.
86 * - Minimal C library globals, if any, will be placed into
88 * - Stack canary globals will be placed into z_libc_partition since
/Zephyr-latest/boards/ezurio/bl5340_dvk/
Dbl5340_dvk_nrf5340_cpuapp_partition_conf.dtsi14 * Secure image will be placed, by default, in flash0
18 * Non-Secure image will be placed in slot0_ns, and use
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/philosophers/src/
Dphil_obj_abstract.h21 * When using dynamic objects, the instances of the fork objects are placed
23 * placed automatically in the forks[] array, the array of references to the
/Zephyr-latest/soc/st/stm32/stm32f0x/
DCMakeLists.txt3 # The vector table must be placed at the start of SRAM
/Zephyr-latest/tests/arch/arm/arm_irq_vector_table/
Dirq-vector-table.ld6 * Some ARM platforms require this symbol to be placed after the IRQ vector
/Zephyr-latest/doc/connectivity/networking/
Dnet_pkt_processing_stats.rst60 * Packet is about to be placed to transmit queue. The time it took from network
74 * Packet is about to be placed to receive queue. The time it took from network
78 * The network packet is then processed and placed to correct socket queue.
/Zephyr-latest/tests/kernel/spinlock/src/
Dspinlock_error_case.c18 * be placed globally in code paths that intel_adsp runs to be valid. Even if
22 * When both are enabled a check to verify that a spin lock is placed
23 * in coherent (uncached) memory is done and asserted on. Spin locks placed
/Zephyr-latest/include/zephyr/input/
Dinput_touch.h27 * This structure **must** be placed first in the driver's config structure.
74 "struct input_touchscreen_common_config must be placed first");
/Zephyr-latest/drivers/i2s/
DKconfig.litex25 bool "Channels placed without padding in fifo"
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/src/
Dphil_obj_abstract.h21 * When using dynamic objects, the instances of the fork objects are placed
23 * placed automatically in the forks[] array, the array of references to the
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst461 struct _isr_list which is placed in a special .intList section.
462 This section is placed in compiled code on precompilation stages only.
481 They are placed in a section with the unique, synthesized name.
482 The name of the section is then placed in .intList section and it is used to create linker script
493 struct _isr_list which is placed in a special .intList section:
542 handler function will be placed here.
544 of the common software IRQ handler is placed here. This code does common
548 spurious IRQ handler will be placed here. The spurious IRQ handler
608 of ``struct _isr_list_sname`` which is placed in a special .intList section:
621 Note that the section name is placed in flexible array member.
[all …]
/Zephyr-latest/drivers/stepper/step_dir/
Dstep_dir_stepper_common.h27 * This structure **must** be placed first in the driver's config structure.
65 * This structure **must** be placed first in the driver's data structure.
118 "struct step_dir_stepper_common_config must be placed first"); \
120 "struct step_dir_stepper_common_data must be placed first");
/Zephyr-latest/drivers/crypto/
Dcrypto_tc_shim_priv.h12 * by the driver. Placed in common location so that crypto applications
/Zephyr-latest/soc/nxp/rw/
Dfirmwares.ld9 * are placed next to each other, the firmware loader will detect the

12345678910>>...13