/Zephyr-latest/lib/os/ |
D | cbprintf_nano.c | 83 char padding_mode, length_mod, special; in z_cbvprintf_impl() local 105 special = 0; in z_cbvprintf_impl() 168 special = *fmt; in z_cbvprintf_impl() 239 } else if (special == ' ') { in z_cbvprintf_impl() 242 } else if (special == '+') { in z_cbvprintf_impl() 268 special = '#'; in z_cbvprintf_impl() 285 if (special == '#') { in z_cbvprintf_impl()
|
/Zephyr-latest/drivers/ethernet/ |
D | eth_e1000_priv.h | 64 uint16_t special; member 74 uint16_t special; member
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | smbus.rst | 30 a three-bytes message to a special address "SMBus Host (0x08)" with own 32 * **SMBALERT# signal**: Peripheral device uses special signal SMBALERT# to 34 from the special "SMBus Alert Response Address (ARA) (0x0c)". The peripheral
|
/Zephyr-latest/boards/common/ |
D | misc.board.cmake | 5 # core on a special-purpose SoC which requires a complicated script to
|
/Zephyr-latest/tests/drivers/build_all/auxdisplay/ |
D | i2c_devices.overlay | 34 special-command-delay-ms = <50>;
|
/Zephyr-latest/drivers/timer/ |
D | Kconfig.xtensa | 13 and CCOMPARE special registers.
|
/Zephyr-latest/drivers/retained_mem/ |
D | Kconfig | 30 memory access is required in an ISR or for special use cases.
|
/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
D | README.txt | 21 No special build options are required to make use of the overlay.
|
/Zephyr-latest/subsys/emul/ |
D | Kconfig | 18 Emulators often implement special features for testing. For example
|
/Zephyr-latest/cmake/modules/ |
D | FindThreads.cmake | 14 # special flags are needed, so this will be empty.
|
/Zephyr-latest/include/zephyr/linker/ |
D | intlist.ld | 7 /* This creates a special section which is not included by the final binary,
|
/Zephyr-latest/doc/build/dts/api/ |
D | api.rst | 10 Some of these -- the ones beginning with ``DT_INST_`` -- require a special 53 There are special-purpose APIs for accessing the :ref:`devicetree-ranges-property`, 69 matching bindings. However, they take on special semantics when the node's 114 There are special-purpose for-each macros, like 125 properties, etc. Some macros used for special purposes (such as 217 and :c:macro:`DT_INST_FOREACH_STATUS_OKAY` are special-purpose helpers without 267 These conveniences may be used for the special-purpose ``fixed-partitions`` 360 The special ``/chosen`` node contains properties whose values describe
|
/Zephyr-latest/samples/subsys/console/getline/ |
D | README.rst | 41 line does not include any special "end of line" characters (like LF, CR,
|
/Zephyr-latest/cmake/bintools/armclang/ |
D | elfconvert_command.cmake | 39 # Note: fromelf is a little special regarding bin output, as each section gets
|
/Zephyr-latest/subsys/retention/ |
D | Kconfig | 34 access is required in an ISR or for special use cases.
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_MMU.txt | 15 "special" ways storing mappings under OS control. Some of these are 35 specified in the RASID special register. The intent is that each 41 in special circumstances, and in any case there is already an invalid 54 number in units of 4 bytes) to the value in the PTEVADDR special 62 This special "refill" fetch is otherwise identical to any other memory 79 one more special trick: it throws a TLB Miss exception (there are two, 117 Thankfully, for the data TLB Xtensa provides 3 special/non-refillable
|
/Zephyr-latest/drivers/interrupt_controller/ |
D | Kconfig.loapic | 20 A special situation may occur when a processor raises its task
|
/Zephyr-latest/samples/subsys/modbus/tcp_server/ |
D | README.rst | 89 This however does not involve any special interaction
|
/Zephyr-latest/boards/starfive/visionfive2/doc/ |
D | index.rst | 69 Press CTRL-A Z for help on special keys
|
/Zephyr-latest/samples/bluetooth/mesh_demo/ |
D | README.rst | 29 A special address, 0x000f, will make the application become a heart-beat
|
/Zephyr-latest/drivers/i2c/ |
D | i2c_dw_registers.h | 96 uint32_t special: 1 __packed; member
|
/Zephyr-latest/doc/build/dts/ |
D | zephyr-user-node.rst | 7 Zephyr's devicetree scripts handle the ``/zephyr,user`` node as a special case:
|
D | macros.bnf | 31 ; The reg property is special and has its own macros. 39 ; The interrupts property is also special. 49 ; The ranges property is also special. 117 ; These are a bit of a special case because they kind of form an array, 302 ; - that are special to the specification ("reg", "interrupts", etc.)
|
/Zephyr-latest/doc/develop/west/ |
D | sign.rst | 26 whitespace or other special characters through all the wrappers can be
|
/Zephyr-latest/samples/subsys/modbus/tcp_gateway/ |
D | README.rst | 93 This however does not involve any special interaction
|