| /f-stack/dpdk/usertools/ |
| H A D | dpdk-devbind.py | 75 devices = {} variable
166 global devices
167 devices = {}
173 global devices
222 devices[d] = devices[d].copy()
274 if dev_name in devices:
291 dev = devices[dev_id]
317 dev = devices[dev_id]
443 global devices
482 devices[d] = dict(devices[d].items() +
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/timer/ |
| H A D | ti,timer.txt | 5 OMAP44xx devices have timer instances that are 100%
6 register compatible with OMAP3xxx devices as well as
8 So for OMAP44xx devices timer instances may use
11 ti,omap2420-timer (applicable to OMAP24xx devices)
12 ti,omap3430-timer (applicable to OMAP3xxx/44xx devices)
13 ti,omap4430-timer (applicable to OMAP44xx devices)
14 ti,omap5430-timer (applicable to OMAP543x devices)
15 ti,am335x-timer (applicable to AM335x devices)
16 ti,am335x-timer-1ms (applicable to AM335x devices)
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sound/ |
| H A D | tlv320aic31xx.txt | 45 * SPL, devices with stereo speaker amp
46 * SPR, devices with stereo speaker amp
47 * SPK, devices with mono speaker amp
51 * MIC1LP, devices with ADC
52 * MIC1RP, devices with ADC
53 * MIC1LM, devices with ADC
54 * AIN1, devices without ADC
55 * AIN2, devices without ADC
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/devices/ |
| H A D | devices_002_neg.ksh | 33 . $STF_SUITE/tests/functional/devices/devices.cfg
34 . $STF_SUITE/tests/functional/devices/devices_common.kshlib
55 log_must zfs set devices=off $TESTPOOL/$TESTFS
|
| H A D | devices_001_pos.ksh | 33 . $STF_SUITE/tests/functional/devices/devices.cfg
34 . $STF_SUITE/tests/functional/devices/devices_common.kshlib
55 log_must zfs set devices=on $TESTPOOL/$TESTFS
|
| H A D | devices_common.kshlib | 31 . $STF_SUITE/tests/functional/devices/devices.cfg
114 log_must zfs set devices=on $TESTPOOL/$TESTFS
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | devbind.rst | 8 that helps binding and unbinding devices from specific drivers.
52 By default, devices which are used by Linux - as indicated by having
62 Due to the way VFIO works, there are certain limitations to which devices can be used with VFIO.
64 …Any Virtual Function device can be used with VFIO on its own, but physical devices will require ei…
68 … should also be unbound from the bridge PCI device for VFIO to work with devices behind the bridge.
97 # Check the status of the available devices.
99 Network devices using DPDK-compatible driver
103 Network devices using kernel driver
112 # Recheck the status of the devices.
114 Network devices using DPDK-compatible driver
|
| /f-stack/dpdk/doc/guides/regexdevs/ |
| H A D | octeontx2.rst | 30 The OCTEON TX2 REE devices will need to be bound to a user-space IO driver
32 used to view the state of the devices and to bind them to a suitable
33 DPDK-supported kernel driver. When querying the status of the devices,
34 they will appear under the category of "REGEX devices", i.e. the command
36 those devices alone.
|
| /f-stack/dpdk/doc/guides/rawdevs/ |
| H A D | octeontx2_ep.rst | 38 The OCTEON TX2 SDP End Point VF devices will need to be bound to a
40 included with DPDK can be used to view the state of the devices and to bind
42 of the devices, they will appear under the category of "Misc (rawdev)
43 devices", i.e. the command ``dpdk-devbind.py --status-dev misc`` can be
44 used to see the state of those devices alone.
67 To perform data transfer using SDP VF EP rawdev devices use standard
73 On EAL initialization, SDP VF devices will be probed and populated into the
74 raw devices. The rawdev ID of the device can be obtained using
|
| H A D | octeontx2_dma.rst | 57 The OCTEON TX2 DPI DMA HW devices will need to be bound to a
59 included with DPDK can be used to view the state of the devices and to bind
61 of the devices, they will appear under the category of "Misc (rawdev)
62 devices", i.e. the command ``dpdk-devbind.py --status-dev misc`` can be
63 used to see the state of those devices alone.
88 To perform data transfer using OCTEON TX2 DMA rawdev devices use standard
94 On EAL initialization, dma devices will be probed and populated into the
95 raw devices. The rawdev ID of the device can be obtained using
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mfd/ |
| H A D | mfd.txt | 3 These devices comprise a nexus for heterogeneous hardware blocks containing
16 mix of unrelated hardware devices.
21 consider all subnodes of the MFD device as separate devices akin to how
23 memory-mapped bus. For more complex devices, when the nexus driver has to
24 probe registers to figure out what child devices exist etc, this should not
25 be used. In the latter case the child devices will be determined by the
|
| /f-stack/freebsd/contrib/device-tree/Bindings/ |
| H A D | common-properties.txt | 65 Daisy-chained devices
68 Many serially-attached GPIO and IIO devices are daisy-chainable. To the
71 by all of its devices. The driver needs to know how many devices the
76 - #daisy-chained-devices: Number of devices in the daisy-chain (default is 1).
84 #daisy-chained-devices = <3>;
|
| H A D | writing-bindings.rst | 31 devices only need child nodes when the child nodes have their own DT
43 strings. DO use fallback compatibles when devices are the same as or a subset
48 properties could be common among devices of the same class. Check other
49 existing bindings for similar devices.
64 - DO put all MMIO devices under a bus node and not at the top-level.
66 - DO use non-empty 'ranges' to limit the size of child buses/devices. 64-bit
67 platforms don't need all devices to have 64-bit address and size.
|
| H A D | xilinx.txt | 3 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
4 in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range
6 devices (gpio, LCD, spi, etc). Also, since these devices are
25 [, (list of compatible devices), ...];
90 device tree. The following are bindings for specific devices:
116 Xilinx Ethernet devices. In addition to general xilinx properties
117 listed above, nodes for these devices should include a phy-handle
123 Xilinx uartlite devices are simple fixed speed serial ports.
130 Xilinx hwicap devices provide access to the configuration logic
146 Xilinx UART 16550 devices are very similar to the NS16550 but with
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/ |
| H A D | mdio.yaml | 34 lines of all devices on that MDIO bus.
38 RESET pulse width in microseconds. It applies to all MDIO devices
39 and must therefore be appropriately determined based on all devices
45 devices and it's determined by how fast all devices are ready for
52 defined 2.5MHz should only be used when all devices on the bus support
58 work, all devices on the bus must support suppressed preamble.
|
| H A D | ti-bluetooth.txt | 5 attached TI Bluetooth devices. The following chips are included in this
8 * TI CC256x Bluetooth devices
9 * TI WiLink 7/8 (wl12xx/wl18xx) Shared Transport BT/FM/GPS devices
11 TI WiLink devices have a UART interface for providing Bluetooth, FM radio,
15 TI WiLink devices also have a separate WiFi interface as described in
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | pmc.txt | 22 - reg: For devices compatible with "fsl,mpc8349-pmc", the first resource
26 For devices compatible with "fsl,mpc8548-pmc", the first resource
29 - interrupts: For "fsl,mpc8349-pmc"-compatible devices, the first
32 - fsl,mpc8313-wakeup-timer: For "fsl,mpc8313-pmc"-compatible devices,
41 supports disabling and resuming devices at any time.
46 This sleep controller only supports disabling devices during system
53 disabling. This sleep controller does not support configuring devices
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | overview.rst | 9 - physical for real devices
10 - virtual for emulated devices
12 Some physical devices may be shaped through a virtual layer as for
17 of these devices.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/keystone/ |
| H A D | keystone.txt | 4 Boards with Keystone2 based devices (TCI66xxK2H) SOC shall have the
8 - compatible: All TI specific devices present in Keystone SOC should be in
9 the form "ti,keystone-*". Generic devices like gic, arch_timers, ns16550
10 type UART should use the specified compatible for those devices.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/misc/ |
| H A D | idt_89hpesx.txt | 1 EEPROM / CSR SMBus-slave interface of IDT 89HPESx devices
6 compatible devices may be produced in future. Following devices
23 - compatible: There are five EEPROM devices supported: 24c32, 24c64, 24c128,
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | link_bonding_poll_mode_drv_lib.rst | 25 creation of bonded devices as well as the configuration and management of the
26 bonded device and its slave devices.
49 the last. Packets are bulk dequeued from devices then serviced in a
143 Bonded devices support the dynamical addition and removal of slave devices using
247 possible, when all slave devices support the same key size.
265 Link bonding devices are created using the ``rte_eth_bond_create`` API
275 Bonding devices support up to a maximum of ``RTE_MAX_ETHPORTS`` slave devices
277 maximum of one bonded device. Slave devices are reconfigured with the
299 the bonded devices MAC address.
428 the bonded devices resources will be allocated on.
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/i3c/ |
| H A D | i3c.txt | 29 values of I2C devices described in the device tree to determine
32 I2C devices
68 I3C devices
71 All I3C devices are supposed to support DAA (Dynamic Address Assignment), and
72 are thus discoverable. So, by default, I3C devices do not have to be described
74 This being said, one might want to attach extra resources to these devices,
76 means we have to describe I3C devices.
80 dynamic address before the DAA takes place (so that other devices on the bus
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/history/ |
| H A D | history_002_pos.ksh | 78 devices on devices off
106 devices on devices off
134 devices on devices off
|
| /f-stack/freebsd/contrib/device-tree/Bindings/input/ |
| H A D | e3x0-button.txt | 9 - "ettus,e3x0-button": For devices such as the NI Ettus Research USRP E3x0
11 - <0 30 1>, <0 31 1>: For devices such as the NI Ettus Research USRP E3x0
13 - "press", "release": For devices such as the NI Ettus Research USRP E3x0
|
| /f-stack/freebsd/contrib/device-tree/Bindings/crypto/ |
| H A D | brcm,spu-crypto.txt | 7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
|