Home
last modified time | relevance | path

Searched full:placement (Results 1 – 25 of 35) sorted by relevance

12

/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/
Ddoxytooltip.css16 .tippy-box[data-theme~='doxytooltip'][data-placement^='top']>.tippy-arrow::before {
20 .tippy-box[data-theme~='doxytooltip'][data-placement^='bottom']>.tippy-arrow::before {
24 .tippy-box[data-theme~='doxytooltip'][data-placement^='left']>.tippy-arrow::before {
28 .tippy-box[data-theme~='doxytooltip'][data-placement^='right']>.tippy-arrow::before {
Ddoxytooltip.js50 placement: 'auto',
/Zephyr-latest/doc/kernel/usermode/
Dmpu_stack_objects.rst13 has implications for the placement of stacks in memory, as well as the
15 implications for placement are directly attributed to the alignment
16 requirements for MPU regions. This is discussed in the memory placement
33 Memory Placement
Dkernelobjects.rst41 Object Placement
106 the object placement criteria will have their memory addresses placed in a
/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/tippy/
Dpopper.min.js7placement,i=o?F(o):null,a=o?U(o):null,s=n.x+n.width/2-r.width/2,f=n.y+n.height/2-r.height/2;switch… property in AnonymousFunction7648dcfe2300.c
Dtippy-bundle.umd.min.js6placement:"top",plugins:[],popperOptions:{},render:null,showOnCreate:!1,touch:!0,trigger:"mouseent…
/Zephyr-latest/boards/segger/ip_k66f/
Dlinker.ld14 * interfaces placement.
18 * Explicit placement of the ethernet interfaces
/Zephyr-latest/boards/raspberrypi/common/
Drpi_pico-led.dtsi7 /* Pico and Pico 2 boards (but not Pico W) have a common LED placement. */
/Zephyr-latest/soc/nxp/mcx/mcxw/
Dlinker.ld19 * We perform all custom placement before including the generic linker file. This
/Zephyr-latest/cmake/linker/
Dlinker_libraries_template.cmake7 # correct placement of those libraries for correct link order.
/Zephyr-latest/subsys/net/l2/wifi/
DCMakeLists.txt20 # Linker section placement for wifi_nm_instance iterable structure
/Zephyr-latest/boards/others/candlelight/doc/
Dindex.rst13 a DB-9M connector for the CAN bus, and two user LEDs. Schematics and component placement drawings
/Zephyr-latest/boards/fysetc/ucan/doc/
Dindex.rst13 terminal block for connecting to the CAN bus, and two user LEDs. Schematics and component placement
/Zephyr-latest/boards/others/candlelightfd/doc/
Dindex.rst13 a DB-9M connector for the CAN bus, and two user LEDs. Schematics and component placement drawings
/Zephyr-latest/dts/bindings/pwm/
Dnxp,s32-emios-pwm.yaml106 edge placement. The period is determined by period of
/Zephyr-latest/boards/adafruit/feather_stm32f405/doc/
Dindex.rst7 Feather standard layout, sharing peripheral placement with other
/Zephyr-latest/doc/hardware/cache/
Dguide.rst102 but provides less control over the placement of these variables, as the linker
/Zephyr-latest/include/zephyr/arch/arm/
Dirq.h231 * is controlled by the placement of
/Zephyr-latest/include/zephyr/
Dirq.h124 * is now controlled by the placement of a ISR_DIRECT_PM() macro, or omitted
/Zephyr-latest/boards/others/stm32_min_dev/doc/
Dindex.rst28 external connectors and placement of components. Many vendors use port PC13/PB12
/Zephyr-latest/arch/xtensa/core/
Dwindow_vectors.S20 * hardware configuration, which is ensured by their placement in a special
/Zephyr-latest/include/zephyr/llext/
Dllext.h329 * instructions on how to rewrite opcodes given the actual placement of some
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst625 and has all the information needed for proper interrupt placement.
671 The isr_tables_swi.ld file describes the placement of the software interrupt table
/Zephyr-latest/tests/net/ptp/clock/src/
Dmain.c295 * placement. in iface_cb()
/Zephyr-latest/drivers/ethernet/
Ddsa_ksz8xxx.c1042 * The order of NET_DEVICE_INIT_INSTANCE() placement IS important.
1045 * the proper placement of eth0, lan1, lan2, lan3, etc - to avoid

12