Home
last modified time | relevance | path

Searched full:internally (Results 1 – 25 of 207) sorted by relevance

123456789

/Zephyr-latest/arch/posix/include/
Dundef_system_defines.h8 * Undefine all system-specific macros defined internally, by the compiler.
9 * Run 'gcc -dM -E - < /dev/null | sort' to get full list of internally
/Zephyr-latest/dts/bindings/serial/
Dnxp,lpuart.yaml15 disconnected, and transmitter output is internally connected to
22 Using this mode, TX and RX lines are internally connected and
Dzephyr,uart-emul.yaml26 Connects TX to RX internally creating a loop back connection. Useful
/Zephyr-latest/drivers/i2s/
DKconfig.sam_ssc35 internally to TF (Transmitter Frame Synchro signal).
46 internally to TK (Transmitter Clock signal).
/Zephyr-latest/tests/drivers/clock_control/nrf_clock_calibration/
DKconfig7 Used internally to enable mocking of temperature sensor
/Zephyr-latest/tests/lib/newlib/thread_safety/src/
Dlocks.c156 * __sinit_lock_acquire() implementation internally uses the in sinit_lock_thread_acq()
173 * __sinit_lock_release() implementation internally uses the in sinit_lock_thread_rel()
226 * __sfp_lock_acquire() implementation internally uses the retargetable in sfp_lock_thread_acq()
243 * __sfp_lock_release() implementation internally uses the retargetable in sfp_lock_thread_rel()
296 * __malloc_lock() implementation internally uses the retargetable in malloc_lock_thread_lock()
313 * __malloc_unlock() implementation internally uses the retargetable in malloc_lock_thread_unlock()
366 * __env_lock() implementation internally uses the retargetable in env_lock_thread_lock()
383 * __env_unlock() implementation internally uses the retargetable in env_lock_thread_unlock()
/Zephyr-latest/doc/kernel/data_structures/
Dslist.rst31 containing struct and the field name of the node. Internally, the
60 the node struct, performing the required offsets internally. And
69 Internally, a :c:type:`sys_slist_t` struct is nothing more than a pair of
112 Internally, the flags are stored unioned with the bottom bits of the
/Zephyr-latest/subsys/net/lib/mqtt_sn/
DKconfig35 int "Maximum number of gateways to store internally"
44 The MQTT_SN library stores addresses internally and thus
/Zephyr-latest/boards/nxp/usb_kw24d512/
DKconfig.defconfig11 # CLK_OUT is internally connected to the input pin EXTAL0
/Zephyr-latest/tests/drivers/dac/dac_loopback/src/
Dtest_dac.c83 * DAC0 output is internally available on ADC0_SE23 when test output
100 /* DAC0 output is internally available on ADC0_SE23 */
115 /* DAC0 output is internally available on ADC0_SE23 */
130 /* DAC0 output is internally available on ADC0_SE4 */
/Zephyr-latest/tests/drivers/spi/spi_loopback/boards/
Dsamd21_xpro.overlay8 /* Internally connect MOSI to MISO for loop-back operation */
Dsamr21_xpro.overlay8 /* Internally connect MOSI to MISO for loop-back operation */
Dsame54_xpro.overlay8 /* Internally connect MOSI to MISO for loop-back operation */
/Zephyr-latest/dts/bindings/w1/
Dzephyr,w1-serial.yaml8 # are internally connected, such that only a single IO
/Zephyr-latest/dts/bindings/spi/
Dnxp,imx-flexspi.yaml56 - 0 # Loopback internally
68 - 0 # Loopback internally
/Zephyr-latest/tests/drivers/uart/uart_async_api/boards/
Dsamc21n_xpro.overlay8 /* Internally loop-back TX and RX on PAD0 */
Dsamd21_xpro.overlay12 /* Internally loop-back TX and RX on PAD0 */
Dsame54_xpro.overlay14 /* Internally loop-back TX and RX on PAD0 */
Dsaml21_xpro.overlay12 /* internally loop-back Tx and Rx on PAD0 */
Dsamr21_xpro.overlay26 /* Internally loop-back TX and RX on PAD0 */
Dsamr34_xpro.overlay29 /* internally loop-back Tx and Rx on PAD0 */
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_hid_internal.h12 * HID device driver API, we can keep internally as long as it is only used in
/Zephyr-latest/drivers/ethernet/phy/
Dphy_adin2111_priv.h16 * @note Used internally by the ADIN offloaded ISR handler.
/Zephyr-latest/drivers/entropy/
DKconfig.npcx22 generated internally and passed to the conditioning component.
/Zephyr-latest/soc/nordic/nrf53/
Dnrf53_cpunet_mgmt.h19 * This function shall be used to control the network CPU exclusively. Internally, it keeps track of

123456789