Home
last modified time | relevance | path

Searched refs:device (Results 4076 – 4100 of 4950) sorted by relevance

1...<<161162163164165166167168169170>>...198

/Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/
Dindex.rst20 - Micro-AB USB device
52 | HWINFO | on-chip | Unique device serial number |
66 | USB | on-chip | USB device |
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/
Dindex.rst26 - Micro-AB USB device
58 | HWINFO | on-chip | Unique device serial number |
72 | USB | on-chip | USB device |
/Zephyr-latest/boards/atmel/sam0/same54_xpro/doc/
Dindex.rst25 - ATECC508 CryptoAuthentication™ device
33 - USB interface, host, and device
163 Authentication device.
/Zephyr-latest/boards/beagle/beaglev_fire/doc/
Dindex.rst34 In order to upload the application to the device, you'll need OpenOCD and GDB
73 Here is the GDB terminal command to connect to the device
126 This will cause the board to appear as a USB mass storage device. You can then then flash the image…
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Daccess.rst145 next time the device reboots, the model's
171 The Composition Data provides information about a mesh device.
172 A device's Composition Data holds information about the elements on the
173 device, the models that it supports, and other features. The Composition
175 information about the device. In order to access this information, the user
182 Composition Data Page 0 provides the fundamental information about a device, and
194 relations can be stored in the composition on a device, and this number should reflect the
/Zephyr-latest/dts/common/nordic/
Dnrf54l20.dtsi246 zephyr,pm-device-runtime-auto;
285 zephyr,pm-device-runtime-auto;
324 zephyr,pm-device-runtime-auto;
519 zephyr,pm-device-runtime-auto;
558 zephyr,pm-device-runtime-auto;
609 zephyr,pm-device-runtime-auto;
/Zephyr-latest/tests/net/virtual/src/
Dmain.c103 const struct device *dev = net_if_get_device(iface); in eth_iface_init()
113 static int eth_tx(const struct device *dev, struct net_pkt *pkt) in eth_tx()
158 static enum ethernet_hw_caps eth_capabilities(const struct device *dev) in eth_capabilities()
181 static int eth_init(const struct device *dev) in eth_init()
201 static uint8_t *net_iface_get_mac(const struct device *dev) in net_iface_get_mac()
229 static int sender_iface(const struct device *dev, struct net_pkt *pkt) in sender_iface()
/Zephyr-latest/doc/releases/
Drelease-notes-3.3.rst14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
256 of the use of zephyr generic device tree ``local-mac-address`` and ``zephyr,random-mac-address``
265 are removed. Related IRQ priorities should now be configured in device tree.
429 * Added a guard to prevent bonding to the same device more than once.
493 * STM32U5: Now supports :ref:`crypto_api` through AES device.
575 expect a 48MHz clock is now done using device tree. When available, HSI48 is enabled
578 since PLL SAI cannot yet be configured using device tree.
582 * The nrf52_bsim (natively simulated nRF52 device with BabbleSim) now models
583 a nRF52833 instead of a nRF52832 device
653 * STM32: HSI48 can now be configured using device tree.
[all …]
Drelease-notes-2.1.rst59 * Added missing Cortex-R CPU device tree bindings.
60 * Fixed incorrect Cortex-R device tree specification.
172 * Added EEPROM device driver API
206 * Converted remaining drivers to device tree
260 * Converted various drivers to device tree
309 * Converted drivers to use device tree
331 * Added CC13xx / CC26xx device drivers for IEEE 802.15.4.
337 network functionality that is not going to be used in the network device.
358 * Network device driver changes for:
505 * :github:`20842` - [Coverity CID :205787] Memory - corruptions in drivers/usb/device/usb\_dc\_nati…
[all …]
/Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/
Dindex.rst98 This should result in a new device "Texas Instruments XDS110 Embed
186 When using OpenOCD from Zephyr SDK to flash the device, you may notice
187 the program hangs when starting the network processor on the device, if the
190 on the board to properly reset the device after flashing.
210 It is available as a Zephyr Wi-Fi device driver in
/Zephyr-latest/drivers/clock_control/
Dclock_stm32_ll_h7.c384 static inline int stm32_clock_control_on(const struct device *dev,
411 static inline int stm32_clock_control_off(const struct device *dev,
432 static inline int stm32_clock_control_configure(const struct device *dev,
460 static int stm32_clock_control_get_subsys_rate(const struct device *clock,
1075 int stm32_clock_control_init(const struct device *dev)
/Zephyr-latest/subsys/fs/
DKconfig63 the underlying storage device is initialized.
105 Enables function fs_mkfs that can be used to format a storage device.
/Zephyr-latest/drivers/spi/
DKconfig69 bool "SPI device statistics"
72 Enable SPI device statistics.
/Zephyr-latest/drivers/modem/
DKconfig.ublox-sara-r488 u-blox SARA-R4 device driver initialization priority.
114 u-blox SARA-R4 device is configured to poll for RSSI
/Zephyr-latest/samples/subsys/ipc/openamp_rsc_table/src/
Dmain_remote.c52 static const struct device *const ipm_handle =
85 static void platform_ipm_callback(const struct device *dev, void *context, in platform_ipm_callback()
/Zephyr-latest/doc/build/dts/
Ddt-vs-kconfig.rst38 As another example, consider a device with a 2.4GHz, multi-protocol radio
64 instance of a hardware device to be used for a particular purpose. An example
/Zephyr-latest/boards/rakwireless/rak11720/doc/
Dindex.rst78 Connect your device to your host computer using the JLINK USB port.
80 Build the Zephyr kernel and application, then flash it to the device:
/Zephyr-latest/boards/mikroe/clicker_2/doc/
Dmikroe_clicker_2.rst53 The two mikroBUS interfaces are aliased in the device tree so that their
74 Error: stm32x device protected
/Zephyr-latest/tests/drivers/mbox/mbox_error_cases/src/
Dmain.c24 static void dummy_callback(const struct device *dev, mbox_channel_id_t channel_id, in dummy_callback()
34 static void dummy_callback_2(const struct device *dev, mbox_channel_id_t channel_id, in dummy_callback_2()
/Zephyr-latest/subsys/secure_storage/
DKconfig16 the device-specific security features that are available and used, the subsystem may
18 This is however highly dependent on the device and configuration in use, and not a
/Zephyr-latest/boards/nxp/frdm_k82f/doc/
Dindex.rst34 - Mass storage device (MSD) flash programming interface
92 | USB | on-chip | USB device |
124 device and host functions through its micro USB connector (J11).
125 Only USB device function is supported in Zephyr at the moment.
/Zephyr-latest/drivers/memc/
Dmemc_sam_smc.c33 static int memc_smc_init(const struct device *dev) in memc_smc_init()
/Zephyr-latest/drivers/gpio/
Dgpio_max149x6.h87 static int max149x6_reg_transceive(const struct device *dev, uint8_t addr, uint8_t val, in max149x6_reg_transceive()
/Zephyr-latest/drivers/w1/
DKconfig24 1-Wire device driver initialization priority.
/Zephyr-latest/soc/infineon/cat1a/
DKconfig43 dual-core MCU. The image is responsible for booting the Cortex-M4 on the device.

1...<<161162163164165166167168169170>>...198