| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/ |
| H A D | coreboot.txt | 13 parameters. It is identified by the magic string "LBIO" in its first
20 is identified by a root node descriptor with the magic number
|
| /f-stack/freebsd/contrib/device-tree/Bindings/regulator/ |
| H A D | 88pm860x.txt | 7 device. Each sub-node is identified using the regulator-compatible
|
| H A D | 88pm800.txt | 7 device. Each sub-node is identified using the node's name (or the deprecated
|
| H A D | isl9305.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| H A D | pv88090.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| H A D | pv88080.txt | 14 device. Each sub-node is identified using the node's name, with valid
|
| H A D | max8907.txt | 15 device. Each sub-node is identified using the node's name (or the deprecated
|
| H A D | pv88060.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| H A D | mcp16502-regulator.txt | 9 the device. Each sub-node is identified using the node's
|
| H A D | tps6586x.txt | 10 device. Each sub-node is identified using the node's name (or the deprecated
|
| H A D | qcom,smd-rpm-regulator.txt | 16 Regulator nodes are identified by their compatible:
242 sub-node is identified using the node's name, with valid values listed for each
|
| H A D | tps65090.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| H A D | da9211.txt | 10 device. Each sub-node is identified using the node's name, with valid
|
| /f-stack/freebsd/contrib/device-tree/Bindings/dma/ |
| H A D | ste-coh901318.txt | 11 COH 901 318 are simple and identified by a single number
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/partitions/ |
| H A D | brcm,bcm963xx-cfe-nor-partitions.txt | 7 at fixed offsets. A valid firmware partition is identified by the ImageTag
|
| /f-stack/freebsd/contrib/device-tree/Bindings/hwmon/ |
| H A D | ltc2978.txt | 33 the device. Each sub-node is identified using the node's name, with valid
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fsi/ |
| H A D | fsi.txt | 69 Slaves are identified by a (link-index, slave-id) pair, so require two cells
94 Engines are identified by their address under the slaves' address spaces. We
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/ |
| H A D | jedec,spi-nor.txt | 10 be identified by the JEDEC READ ID opcode (0x9F).
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mfd/ |
| H A D | qcom-rpm.txt | 54 Regulator nodes are identified by their compatible:
153 sub-node is identified using the node's name, with valid values listed for each
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | kirkwood-b3.dts | 89 * Not yet identified what it is, maybe the eeprom
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 91 identified and the corresponding device number can be used to tune various PF
|
| /f-stack/dpdk/doc/guides/rawdevs/ |
| H A D | ifpga.rst | 97 is identified by this parameter.
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | hash_lib.rst | 11 …tructure optimized for searching through a set of entries that are each identified by a unique key.
65 …ations define which port to forward a packet to based on a packet flow identified by the five-tupl…
137 Once the buckets are identified, the scope of the key add,
149 First of all, the primary bucket is identified and entry is likely to be stored there.
157 Like lookup, the primary and secondary buckets are identified. If there is an empty entry in
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/qcom/ |
| H A D | qcom,smp2p.txt | 6 identified in the system by the directed edge (local processor ID to remote
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pci/ |
| H A D | pci-iommu.txt | 4 Each PCI(e) device under a root complex is uniquely identified by its Requester
|