Lines Matching +full:device +full:- +full:id
3 Contact: linux-pci@vger.kernel.org
5 Writing a device location to this file will cause
6 the driver to attempt to bind to the device found at
9 That is Domain:Bus:Device.Function and is the same as
14 (Note: kernels before 2.6.28 may require echo -n).
18 Contact: linux-pci@vger.kernel.org
20 Writing a device location to this file will cause the
21 driver to attempt to unbind from the device found at
24 That is Domain:Bus:Device.Function and is the same as
29 (Note: kernels before 2.6.28 may require echo -n).
33 Contact: linux-pci@vger.kernel.org
35 Writing a device ID to this file will attempt to
36 dynamically add a new device ID to a PCI device driver.
38 was included in the driver's static device ID support
39 table at compile time. The format for the device ID is:
40 VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID,
41 Device ID, Subsystem Vendor ID, Subsystem Device ID,
42 Class, Class Mask, and Private Driver Data. The Vendor ID
43 and Device ID fields are required, the rest are optional.
44 Upon successfully adding an ID, the driver will probe
45 for the device and attempt to bind to it. For example::
51 Contact: Chris Wright <chrisw@sous-sol.org>
53 Writing a device ID to this file will remove an ID
55 The format for the device ID is:
56 VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device
57 ID, Subsystem Vendor ID, Subsystem Device ID, Class,
58 and Class Mask. The Vendor ID and Device ID fields are
60 removing an ID, the driver will no longer support the
61 device. This is useful to ensure auto probing won't
62 match the driver to the device. For example::
68 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
70 Writing a non-zero value to this attribute will
72 re-discover previously removed devices.
76 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
79 MSI-X for any future drivers of the device. If the device
80 is a bridge, MSI and MSI-X will be disallowed for future
90 irq vector allocated to that device.
101 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
103 Writing a non-zero value to this attribute will
104 hot-remove the PCI device and any of its children.
108 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
110 Writing a non-zero value to this attribute will
112 and re-discover devices removed earlier from this
113 part of the device tree.
117 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
119 Writing a non-zero value to this attribute will
120 force a rescan of the device's parent bus and all
121 child buses, and re-discover devices removed earlier
122 from this part of the device tree.
129 without affecting other functions in the same device.
138 A file named vpd in a device directory will be a
140 device. It should follow the VPD format defined in
150 This symbolic link appears when hardware supports the SR-IOV
152 The symbolic link points to the PCI device sysfs entry of the
153 Virtual Function whose index is N (0...MaxVFs-1).
159 This symbolic link appears when hardware supports the SR-IOV
161 and this device has vendor specific dependencies with others.
162 The symbolic link points to the PCI device sysfs entry of
163 Physical Function this device depends on.
169 This symbolic link appears when a device is a Virtual Function.
170 The symbolic link points to the PCI device sysfs entry of the
171 Physical Function this device associates with.
175 Contact: linux-pci@vger.kernel.org
182 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
186 the PCI device. The attribute will be created only
187 if the firmware has given a name to the PCI device.
192 firmware assigned name of the PCI device.
196 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
199 given instance (SMBIOS type 41 device type instance) of the
200 PCI device. The attribute will be created only if the firmware
201 has given an instance number to the PCI device.
204 firmware assigned device type instance of the PCI
205 device that can help in understanding the firmware
206 intended order of the PCI device.
210 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
213 given instance (ACPI _DSM instance number) of the PCI device.
215 an instance number to the PCI device. ACPI _DSM instance number
217 type 41 device type instance also.
221 device that can help in understanding the firmware
222 intended order of the PCI device.
229 device can be put into D3Cold state. If it is cleared, the
230 device will never be put into D3Cold state. If it is set, the
231 device may be put into D3Cold state if other requirements are
240 This file appears when a physical PCIe device supports SR-IOV.
244 in the PF's SR-IOV extended capability structure's TotalVFs
253 This file appears when a physical PCIe device supports SR-IOV.
274 This file allows the driver for a device to be specified which
275 will override standard static and dynamic ID matching. When
278 device. The override is specified by writing a string to the
279 driver_override file (echo pci-stub > driver_override) and
281 This returns the device to standard matching rules binding.
283 device from its current driver or make any attempt to
285 matching name is currently loaded in the kernel, the device
287 opt-out of driver binding using a driver_override name such as
295 This file contains the NUMA node to which the PCI device is
296 attached, or -1 if the node is unknown. The initial value
308 This file contains the revision field of the PCI device.
309 The value comes from device config space. The file is read only.
315 This file is associated with the PF of a device that
316 supports SR-IOV. It determines whether newly-enabled VFs
324 VFs, then assign the newly-created VFs to virtual machines.
325 Note that changing this file does not affect already-
327 the VFs, write 0 to sriov_drivers_autoprobe, then re-enable
337 If the device has any Peer-to-Peer memory registered, this
338 file contains the total amount of memory that the device
345 If the device has any Peer-to-Peer memory registered, this
353 If the device has any Peer-to-Peer memory registered, this
355 use outside the driver that owns the device.