Home
last modified time | relevance | path

Searched refs:devices (Results 1 – 25 of 506) sorted by relevance

12345678910>>...21

/Zephyr-Core-3.5.0/modules/hal_infineon/
DKconfig12 Enable Analog-to-Digital Converter (ADC) HAL module driver for Infineon devices
17 Enable Inter-Integrated Circuit Interface (I2C) HAL module driver for Infineon devices
22 Enable Real-Time Clock (RTC) HAL module driver for Infineon devices
27 Enable Secure Digital Input/Output interface (SDIO) HAL module for Infineon devices
33 Enable Serial Peripheral Interface (SPI) HAL module driver for Infineon devices
39 Enable Timer (Timer/Counter) HAL module driver for Infineon devices
44 Enable Low-Power Timer (LPTimer) HAL module driver for Infineon devices
49 Enable True Random Number Generator (TRNG) HAL module driver for Infineon devices
55 driver for Infineon devices
61 driver for Infineon devices
[all …]
DCMakeLists.txt10 ## Add PDL sources for XMC devices
16 ## Add core-lib sources for CAT1 devices
19 ## Add mtb-pdl-cat1 sources for CAT1 devices
22 ## Add mtb-templates-cat1 sources for CAT1 devices
27 ## Add mtb-hal-cat1 sources for CAT1 devices
39 ## Add btstack-integration for CYW43xx BT devices
/Zephyr-Core-3.5.0/scripts/build/
Delf_parser.py125 self.devices = []
185 def _link_devices(self, devices): argument
191 for ord, dev in devices.items():
197 if dn.dep_ordinal in devices:
199 dev.devs_depends_on.add(devices[dn.dep_ordinal])
208 if sn.dep_ordinal in devices:
209 dev.devs_supports.add(devices[sn.dep_ordinal])
215 def _link_injected(self, devices): argument
216 for dev in devices.values():
219 if inj in devices:
[all …]
/Zephyr-Core-3.5.0/soc/arm/st_stm32/stm32f1/
DKconfig.soc47 * Low density Value line devices
48 * Medium density Value line devices
49 * High density Value line devices
50 * XL-density devices Value line devices
55 Connectivity line devices are STM32F105xx and STM32F107xx
/Zephyr-Core-3.5.0/tests/drivers/counter/counter_nrf_rtc/fixed_top/src/
Dtest_counter_fixed_top.c26 static const struct device *const devices[] = { variable
58 for (int i = 0; i < ARRAY_SIZE(devices); i++) { in test_all_instances()
59 counter_setup_instance(devices[i]); in test_all_instances()
61 counter_tear_down_instance(devices[i]); in test_all_instances()
69 const struct device *dev = devices[idx]; in test_set_custom_top_value_fails_on_instance()
94 const struct device *dev = devices[idx]; in test_top_handler_on_instance()
/Zephyr-Core-3.5.0/subsys/bluetooth/services/ias/
Dias.c39 static struct alerting_device devices[CONFIG_BT_MAX_CONN]; variable
48 if (alert_level < devices[i].alert_level) { in set_alert_level()
49 alert_level = devices[i].alert_level; in set_alert_level()
85 devices[bt_conn_index(conn)].alert_level = BT_IAS_ALERT_LVL_NO_ALERT; in disconnected()
96 devices[idx].alert_level = BT_IAS_ALERT_LVL_NO_ALERT; in bt_ias_local_alert_stop()
120 devices[bt_conn_index(conn)].alert_level = alert_val; in bt_ias_write_alert_lvl()
/Zephyr-Core-3.5.0/scripts/pylib/pytest-twister-harness/src/twister_harness/
Dtwister_harness_config.py38 devices: list[DeviceConfig] = field(default_factory=list, repr=False) variable in TwisterHarnessConfig
44 devices = []
66 devices.append(device_from_cli)
69 devices=devices
/Zephyr-Core-3.5.0/samples/drivers/w1/scanner/
DREADME.rst5 Scan for 1-Wire devices and print their family ID and serial number.
10 This sample demonstrates how to scan for 1-Wire devices. It runs the 1-Wire
12 devices found.
35 [00:00:00.656,097] <inf> main: Number of devices found on bus: 3
/Zephyr-Core-3.5.0/soc/x86/intel_ish/doc/
Dsupported_features.txt4 In addition to the standard architecture devices (HPET, local and I/O APICs,
5 etc.), Zephyr supports the following ISH-specific SoC devices:
/Zephyr-Core-3.5.0/scripts/west_commands/runners/
Dbossac.py236 devices = self.get_darwin_serial_device_list()
238 if len(devices) == 0:
240 elif len(devices) == 1:
241 print('Using only serial device on the system: ' + devices[0])
242 return devices[0]
252 for i, device in enumerate(devices, 1):
266 if 1 <= value <= len(devices):
269 return devices[value - 1]
/Zephyr-Core-3.5.0/drivers/interrupt_controller/
DKconfig.xmc4xxx7 bool "Interrupt Controller Driver for XMC4XXX series devices"
11 Enable interrupt controller driver for XMC4XXX series of devices. This is required for
DKconfig.sam07 bool "External Interrupt Controller (EIC) Driver for SAM0 series devices"
11 Enable EIC driver for SAM0 series of devices. This is required for
/Zephyr-Core-3.5.0/soc/x86/elkhart_lake/doc/
Dsupported_features.txt4 In addition to the standard architecture devices (HPET, local and I/O APICs,
5 etc.), Zephyr supports the following Elkhart Lake-specific SoC devices:
/Zephyr-Core-3.5.0/soc/x86/raptor_lake/doc/
Dsupported_features.txt4 In addition to the standard architecture devices (HPET, local and I/O APICs,
5 etc.), Zephyr supports the following Raptor Lake-specific SoC devices:
/Zephyr-Core-3.5.0/soc/x86/alder_lake/doc/
Dsupported_features.txt4 In addition to the standard architecture devices (HPET, local and I/O APICs,
5 etc.), Zephyr supports the following Alder Lake-specific SoC devices:
/Zephyr-Core-3.5.0/doc/services/pm/
Dpower_domain.rst9 The Zephyr power domain abstraction is designed to support groupings of devices
19 power domain to notify all devices using it through their power management
52 Most of the devices in an SoC have independent power control that can
56 normally are divided into several regions grouping devices that
67 or a dedicated power IC. Multiple devices can be powered from the same source,
68 and this grouping of devices is typically called a "power domain".
70 Placing devices on power domains can be done for a variety of reasons,
71 including to enable devices with high power consumption in low power mode to be
90 PM subsystem to turn devices on and off.
126 ``power-domain`` node's property. The example below declares devices
[all …]
Ddevice.rst7 Device power management (PM) on Zephyr is a feature that enables devices to
23 In this method, the application or any component that deals with devices directly
25 saves power if some devices that are not in use can be turned off or put
27 active. The components that use the devices need to be power aware and should
33 devices are already put in the appropriate power state by the application or
34 component managing the devices.
47 subsystem will suspend devices before changing state. The subsystem takes care
48 of suspending devices following their initialization order, ensuring that
50 from a sleep state, devices are resumed in the opposite order that they were
79 state and devices are resumed by the first core that becomes active.
[all …]
/Zephyr-Core-3.5.0/tests/drivers/clock_control/clock_control_api/src/
Dtest_clock_control.c48 static const struct device_data devices[] = { variable
138 for (size_t i = 0; i < ARRAY_SIZE(devices); i++) { in test_all_instances()
139 for (size_t j = 0; j < devices[i].subsys_cnt; j++) { in test_all_instances()
140 zassert_true(device_is_ready(devices[i].dev), in test_all_instances()
141 "Device %s is not ready", devices[i].dev->name); in test_all_instances()
142 test_with_single_instance(devices[i].dev, in test_all_instances()
143 devices[i].subsys_data[j].subsys, in test_all_instances()
144 devices[i].subsys_data[j].startup_us, in test_all_instances()
/Zephyr-Core-3.5.0/drivers/i3c/
Di3c_common.c96 sys_slist_init(&data->attached_dev.devices.i3c); in i3c_addr_slots_init()
97 sys_slist_init(&data->attached_dev.devices.i2c); in i3c_addr_slots_init()
205 SYS_SLIST_FOR_EACH_NODE(&dev_list->devices.i3c, node) { in i3c_dev_list_i3c_addr_find()
225 SYS_SLIST_FOR_EACH_NODE(&dev_list->devices.i2c, node) { in i3c_dev_list_i2c_addr_find()
303 if (!sys_slist_is_empty(&data->attached_dev.devices.i3c)) { in i3c_attach_i3c_device()
304 SYS_SLIST_FOR_EACH_NODE(&data->attached_dev.devices.i3c, node) { in i3c_attach_i3c_device()
316 sys_slist_append(&data->attached_dev.devices.i3c, &target->node); in i3c_attach_i3c_device()
357 if (!sys_slist_is_empty(&data->attached_dev.devices.i3c)) { in i3c_detach_i3c_device()
358 if (!sys_slist_find_and_remove(&data->attached_dev.devices.i3c, &target->node)) { in i3c_detach_i3c_device()
383 if (!sys_slist_is_empty(&data->attached_dev.devices.i2c)) { in i3c_attach_i2c_device()
[all …]
/Zephyr-Core-3.5.0/subsys/pm/
DKconfig44 When this option is enabled, check that no devices are busy before
93 devices that depend on a domain will be notified when this
97 bool "Dynamically bind devices to a Power Pomain"
100 Enable support for dynamically bind devices to a Power Domain.
103 int "Number of devices that can dynamically be bind to a Power Domain"
107 The number of devices that can dynamically be bind to a Power Domain.
114 enabled, devices can be suspended or resumed based on the device
123 only rely on Runtime PM to manage the devices power states.
/Zephyr-Core-3.5.0/drivers/spi/
DKconfig.spi_emul12 drivers that pretend to be devices on the emulated SPI bus. It is
13 used for testing drivers for SPI devices.
/Zephyr-Core-3.5.0/drivers/i2c/
DKconfig.i2c_emul12 drivers that pretend to be devices on the emulated I2C bus. It is
13 used for testing drivers for I2C devices.
/Zephyr-Core-3.5.0/samples/bluetooth/direct_adv/
DREADME.rst12 provides two BLE characteristics. To perform write, devices need to be bonded, while read
15 Please note that direct advertising towards iOS based devices is not allowed.
16 For more information about designing BLE devices for Apple products refer to
/Zephyr-Core-3.5.0/drivers/mfd/
DKconfig7 Include drivers for multi-function devices
19 Multi-function devices initialization priority.
/Zephyr-Core-3.5.0/drivers/auxdisplay/
DKconfig14 int "Auxiliary display devices init priority"
17 Auxiliary (textual) display devices initialization priority.

12345678910>>...21