Searched refs:device (Results 4101 – 4125 of 4950) sorted by relevance
1...<<161162163164165166167168169170>>...198
/Zephyr-latest/drivers/misc/ft8xx/ |
D | ft8xx_drv.c | 30 __weak void ft8xx_drv_irq_triggered(const struct device *dev, in ft8xx_drv_irq_triggered()
|
/Zephyr-latest/drivers/modem/ |
D | Kconfig.wncm14a2a | 43 WNC-M14A2A device driver initialization priority.
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | fuel_gauge.rst | 18 Fundamentally, a property is a quantity that a fuel gauge device can measure.
|
/Zephyr-latest/samples/drivers/display/ |
D | README.rst | 5 Draw basic rectangles on a display device.
|
/Zephyr-latest/samples/subsys/fs/format/ |
D | README.rst | 14 * littleFS on flash device
|
/Zephyr-latest/samples/subsys/ipc/ipc_service/icmsg/src/ |
D | main.c | 132 const struct device *ipc0_instance; in main()
|
/Zephyr-latest/soc/st/stm32/stm32wbax/hci_if/ |
D | linklayer_plat_adapt.c | 25 extern const struct device *rng_dev;
|
/Zephyr-latest/modules/hal_nordic/nrf_802154/serialization/platform/ |
D | nrf_802154_spinel_backend_ipc.c | 58 const struct device *const ipc_instance = in nrf_802154_backend_init()
|
/Zephyr-latest/samples/arch/mpu/mpu_test/src/ |
D | main.c | 34 static const struct device *const flash_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_flash_controller));
|
/Zephyr-latest/tests/drivers/sdhc/ |
D | README.txt | 4 This test is designed to verify the functionality of a device implementing the
|
/Zephyr-latest/samples/boards/st/mco/ |
D | README.rst | 37 The clock can be observed using a probing device, such as a logic analyzer.
|
/Zephyr-latest/tests/lib/gui/lvgl/src/ |
D | main.c | 59 static const struct device *display_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_display));
|
/Zephyr-latest/tests/kernel/device/boards/ |
D | hifive_unmatched_fu740_s7.overlay | 7 * Application overlay for creating a fake device instance we
|
D | hifive_unmatched_fu740_u74.overlay | 7 * Application overlay for creating a fake device instance we
|
/Zephyr-latest/boards/nxp/lpcxpresso54114/ |
D | lpcxpresso54114_lpc54114_m4.dts | 54 * application can have an application specific device tree to
|
/Zephyr-latest/tests/subsys/dfu/mcuboot_multi/src/ |
D | main.c | 24 const struct device *sf_dev; in erase_image_status_page()
|
/Zephyr-latest/arch/x86/core/intel64/ |
D | irq.c | 31 static const struct device *const vtd = DEVICE_DT_GET_ONE(intel_vt_d);
|
/Zephyr-latest/tests/drivers/mbox/mbox_data/src/ |
D | main.c | 51 static void callback(const struct device *dev, uint32_t channel, void *user_data, in callback()
|
/Zephyr-latest/subsys/net/lib/tls_credentials/ |
D | Kconfig | 53 device's secure file system; eg, via a vendor tool or
|
/Zephyr-latest/doc/services/storage/zms/ |
D | zms.rst | 115 * erase-blocks if the device has erase capabilities 121 /** Flash device runtime structure */ 122 const struct device *flash_device; 293 As an example, to erase a 4096 bytes sector on a non-erasable device using NVS, 256 flash writes 299 To make the garbage collector not affect the life expectancy of the device it is recommended 314 A typical scenario is shown here to calculate the life expectancy of a device: 337 The expected life of the device in minutes is computed as : 349 ``MAX_NUM_WRITES``: is the life expectancy of the storage device in number of writes 383 - Add the possibility to retrieve the wear out value of the device based on the cycle count value 398 - If you are using a non-erasable technology device like RRAM or MRAM, :ref:`ZMS <zms_api>` is defi… [all …]
|
/Zephyr-latest/doc/build/dts/ |
D | api-usage.rst | 20 parsed at runtime, for example to load and initialize device drivers. 51 refer to *some* device of a particular type ("the board's user LED") but 57 This is done primarily by device drivers, as instance numbers are a way to 291 a device driver. 313 phandle to a Zephyr driver-level :ref:`struct device <device_model_api>`. 314 See :ref:`dt-get-device` for ways to do that. 346 Special purpose macros are available for writing device drivers, which usually
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.ipv4 | 9 Enable IPv4 support. If this is enabled then the device is 50 The value should normally be > 0. The device receiving the IPv4 60 The value should normally be > 0. The device receiving the IPv4
|
/Zephyr-latest/drivers/lora/ |
D | sx127x.c | 93 #error No SX127x instance in device tree. 339 static void sx127x_irq_callback(const struct device *dev, in sx127x_irq_callback() 580 static int sx127x_lora_init(const struct device *dev) in sx127x_lora_init()
|
/Zephyr-latest/boards/seco/stm32f3_seco_d23/doc/ |
D | index.rst | 72 | USB | on-chip | USB device | 159 SECO SBC-3.5-PX30 has a USB 2.0 full-speed device interface available through 212 $ minicom -D /dev/<tty device>
|
/Zephyr-latest/drivers/espi/ |
D | Kconfig | 129 bool "Host peripheral device support EC host command subsystem" 135 bool "Host peripheral device support shared memory region" 152 bool "Host peripheral device support customized opcode"
|
1...<<161162163164165166167168169170>>...198