Home
last modified time | relevance | path

Searched full:deviceid (Results 1 – 13 of 13) sorted by relevance

/Documentation/filesystems/nfs/
Dpnfs.rst38 RCU is used because the deviceid is basically a write once, read many
41 deviceid's per filesystem, and multiple filesystems per nfs_client.
51 level cache. Its reference is held over the lifetime of the deviceid
/Documentation/PCI/endpoint/
Dpci-ntb-howto.rst66 baseclass_code deviceid msi_interrupts pci-epf-ntb.0
85 to change the vendorid and the deviceid, the following
89 # echo 0xb00d > functions/pci_epf_ntb/func1/deviceid
Dpci-vntb-howto.rst62 baseclass_code deviceid msi_interrupts pci-epf-ntb.0
81 to change the vendorid and the deviceid, the following
85 # echo 0x0809 > functions/pci_epf_vntb/func1/deviceid
Dpci-endpoint-cfs.rst63 ... deviceid
127 | deviceid
Dpci-test-howto.rst63 deviceid msix_interrupts subclass_code vendorid
83 # echo 0xb500 > functions/pci_epf_test/func1/deviceid
/Documentation/devicetree/bindings/virtio/
Dvirtio-device.yaml21 "virtio,deviceID", where ID is the virtio device id. The textual
/Documentation/PCI/endpoint/function/binding/
Dpci-test.rst13 deviceid should be 0xb500 for DRA74x and 0xb501 for DRA72x
Dpci-ntb.rst13 deviceid should be 0xb00d for TI's J721E SoC
/Documentation/devicetree/bindings/bus/
Dxlnx,versal-net-cdx.yaml19 (one to one associated with the device). The streamid and deviceid
/Documentation/virt/kvm/devices/
Darm-vgic-its.rst151 The device table and ITT are indexed by the DeviceID and EventID,
166 corresponds to the DeviceID offset to the next DTE, capped by
/Documentation/devicetree/bindings/misc/
Dfsl,qoriq-mc.yaml120 between the ICID and deviceID this property can be used
/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic-v3.yaml212 The single msi-cell is the DeviceID of the device which will generate
/Documentation/accel/qaic/
Daic100.rst33 DeviceID(DID) combination to uniquely identify itself to the host. AIC100