Home
last modified time | relevance | path

Searched full:interacting (Results 1 – 25 of 29) sorted by relevance

12

/Zephyr-Core-3.5.0/drivers/serial/
DKconfig.native_tty4 bool "UART driver for interacting with host serial ports"
Duart_native_tty.c2 * @brief UART Driver for interacting with host serial ports
/Zephyr-Core-3.5.0/drivers/regulator/
DKconfig23 Enable regulator shell framework, for interacting with regulators via
/Zephyr-Core-3.5.0/cmake/modules/
Dpython.cmake6 # interacting with a terminal. This is required since Python scripts
/Zephyr-Core-3.5.0/subsys/input/
DKconfig81 Enable the input shell, for interacting with the input subsystem
/Zephyr-Core-3.5.0/scripts/native_simulator/common/src/include/
Dnsi_host_trampolines.h8 * These are intended to facilitate test embedded code interacting with the host.
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dsdhc.rst7 The SDHC api offers a generic interface for interacting with an SD host
/Zephyr-Core-3.5.0/dts/bindings/i2c/
Dnordic,nrf-twim.yaml38 This property must be provided when interacting with devices like
/Zephyr-Core-3.5.0/samples/bluetooth/mesh/
DREADME.rst53 Interacting with the sample
/Zephyr-Core-3.5.0/modules/hal_infineon/mtb-hal-cat1/
DCMakeLists.txt68 # High level interface for interacting with CAT1 hardware
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst13 Node Provisioning Protocol Interface procedures by interacting with mesh nodes that support the
Ddfu.rst177 network by interacting with the web server pointed to in the URI. The URI must point to a
/Zephyr-Core-3.5.0/drivers/memc/
Dmemc_mcux_flexspi_s27ks0641.c17 * called while interacting with the flexspi MUST be relocated to SRAM or ITCM
Dmemc_mcux_flexspi.c20 * called while interacting with the flexspi MUST be relocated to SRAM or ITCM
Dmemc_mcux_flexspi_aps6408l.c22 * called while interacting with the flexspi MUST be relocated to SRAM or ITCM
/Zephyr-Core-3.5.0/samples/bluetooth/hci_uart_async/
DREADME.rst73 interacting with the controller and instead just be aware of it in order
/Zephyr-Core-3.5.0/boards/posix/native_sim/doc/
Dindex.rst80 you will be able to test your code interacting with that C library,
/Zephyr-Core-3.5.0/samples/bluetooth/hci_uart/
DREADME.rst80 interacting with the controller and instead just be aware of it in order
/Zephyr-Core-3.5.0/include/zephyr/drivers/
Dlora.h104 * interacting with a public network.
/Zephyr-Core-3.5.0/boards/posix/native_posix/doc/
Dindex.rst195 interacting with external interfaces based on the real host time.
282 An UART driver for interacting with host-attached serial port devices
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Dbluetooth-tools.rst19 The recommended mobile applications for interacting with Zephyr are:
/Zephyr-Core-3.5.0/drivers/watchdog/
Dwdt_nxp_fs26.c216 * @param spi SPI specs for interacting with the device
237 * @param spi SPI specs for interacting with the device
/Zephyr-Core-3.5.0/drivers/flash/
Dflash_mcux_flexspi_mx25um51345g.c28 * called while interacting with the flexspi MUST be relocated to SRAM or ITCM
Dflash_mcux_flexspi_nor.c29 * called while interacting with the flexspi MUST be relocated to SRAM or ITCM
/Zephyr-Core-3.5.0/doc/connectivity/networking/conn_mgr/
Dimplementation.rst274 Connectivity implementations should not prevent applications from interacting directly with associa…

12