Home
last modified time | relevance | path

Searched full:capable (Results 1 – 25 of 210) sorted by relevance

123456789

/Zephyr-latest/include/zephyr/net/
Dmii.h83 /** 100BASE-T4 capable */
85 /** 100BASE-X full duplex capable */
87 /** 100BASE-X half duplex capable */
89 /** 10 Mb/s full duplex capable */
91 /** 10 Mb/s half duplex capable */
93 /** 100BASE-T2 full duplex capable */
95 /** 100BASE-T2 half duplex capable */
153 /** 1000BASE-X full-duplex capable */
155 /** 1000BASE-X half-duplex capable */
157 /** 1000BASE-T full-duplex capable */
[all …]
/Zephyr-latest/dts/bindings/base/
Dpm.yaml13 device that tells the system that the device is capable of
16 Wake up capable devices are disabled (interruptions will not wake up
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
DKconfig23 Enable to mark the whole system as Grand Master Capable.
126 considered capable of participating in the IEEE 802.1AS protocol.
192 master capable, and 248 if it is GM capable.
194 of priority1. Note that if the system is non GM capable, then the
/Zephyr-latest/snippets/xen_dom0/boards/
Drcar_salvator_xs.overlay17 * is not capable to parse and handle it in runtime.
35 * is not capable to parse and handle it in runtime.
Dqemu_cortex_a53.overlay21 * is not capable to parse and handle it in runtime.
39 * is not capable to parse and handle it in runtime.
Drcar_h3ulcb_r8a77951_a57.overlay17 * is not capable to parse and handle it in runtime.
35 * is not capable to parse and handle it in runtime.
Drcar_spider_s4_r8a779f0_a55.overlay19 * is not capable to parse and handle it in runtime.
37 * is not capable to parse and handle it in runtime.
/Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/src/
Dmain.c35 printk("Device is not wakeup capable\n"); in main()
37 printk("Device is wakeup capable\n"); in main()
/Zephyr-latest/dts/bindings/interrupt-controller/
Dmicrochip,xec-ecia.yaml14 direct-capable-girqs:
/Zephyr-latest/doc/hardware/peripherals/
Dsdhc.rst17 An SD host controller is a device capable of sending SD commands to an attached
19 Some SD host controllers are also capable of communicating with MMC devices.
Dmbox.rst9 An MBOX device is a peripheral capable of passing signals (and data depending
/Zephyr-latest/drivers/led/
DKconfig.is31fl373311 IS31FL3733 is a matrix LED driver, capable of a maximum of 3.29 mA
/Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/
Dsample.yaml12 - "Device is wakeup capable"
/Zephyr-latest/dts/bindings/sensor/
Dplantower,pms7003.yaml6 Air pollution sensor capable of measuring mass concentration of dust. See
Dphosense,xbr818.yaml5 Phosense XBR818 I2C-capable 10 GHz Radar Sensor
/Zephyr-latest/dts/bindings/dma/
Dsilabs,ldma.yaml8 capable of supporting 8 independent DMA channels. It supports specific
Dwch,wch-dma.yaml9 Every channel is capable of memory-to-memory, memory-to-peripheral, and
Dst,stm32-dma.yaml8 capable of supporting 5 or 6 or 7 or 8 independent DMA channels.
/Zephyr-latest/lib/os/
DKconfig35 Enable usage of mpsc packet buffer. Packet buffer is capable of
42 Enable usage of spsc packet buffer. Packet buffer is capable of
/Zephyr-latest/include/zephyr/dt-bindings/pinctrl/renesas/
Dpinctrl-rcar-common.h27 /* Arbitrary number to encode non capable gpio pin */
31 * @brief Utility macro to encode a GPIO capable pin
39 * @brief Utility macro to encode a non capable GPIO pin
/Zephyr-latest/samples/drivers/i2c/custom_target/
DREADME.rst16 This sample requires an I2C peripheral which is capable of acting as a target.
/Zephyr-latest/drivers/flash/
DKconfig.at4519 The driver is only capable of using "power of 2" binary page sizes
/Zephyr-latest/samples/drivers/i2c/target_eeprom/
DREADME.rst16 This sample requires an I2C peripheral which is capable of acting as a target.
/Zephyr-latest/dts/bindings/watchdog/
Dgd,gd32-fwdgt.yaml26 Validate the value is within a capable range at the compile time.
/Zephyr-latest/dts/bindings/gpio/
Dmicrobit,edge-connector.yaml12 input and output (GPIO) and are also capable of analog, PWM and touch

123456789