Lines Matching +full:device +full:- +full:id
4 Contact: linux-pci@vger.kernel.org
6 Writing a device location to this file will cause
7 the driver to attempt to bind to the device found at
10 That is Domain:Bus:Device.Function and is the same as
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
22 Writing a device location to this file will cause the
23 driver to attempt to unbind from the device found at
26 That is Domain:Bus:Device.Function and is the same as
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-pci@vger.kernel.org
38 Writing a device ID to this file will attempt to
39 dynamically add a new device ID to a PCI device driver.
41 was included in the driver's static device ID support
42 table at compile time. The format for the device ID is:
43 VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID,
44 Device ID, Subsystem Vendor ID, Subsystem Device ID,
45 Class, Class Mask, and Private Driver Data. The Vendor ID
46 and Device ID fields are required, the rest are optional.
47 Upon successfully adding an ID, the driver will probe
48 for the device and attempt to bind to it. For example::
55 Contact: Chris Wright <chrisw@sous-sol.org>
57 Writing a device ID to this file will remove an ID
59 The format for the device ID is:
60 VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device
61 ID, Subsystem Vendor ID, Subsystem Device ID, Class,
62 and Class Mask. The Vendor ID and Device ID fields are
64 removing an ID, the driver will no longer support the
65 device. This is useful to ensure auto probing won't
66 match the driver to the device. For example::
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
83 MSI-X for any future drivers of the device. If the device
84 is a bridge, MSI and MSI-X will be disallowed for future
94 irq vector allocated to that device.
105 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
107 If a driver has enabled MSI (not MSI-X), "irq" contains the
111 "irq" being set to 0 indicates that the device isn't
116 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
118 Writing a non-zero value to this attribute will
119 hot-remove the PCI device and any of its children.
123 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
125 Writing a non-zero value to this attribute will
127 and re-discover devices removed earlier from this
128 part of the device tree.
132 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
134 Writing a non-zero value to this attribute will
135 force a rescan of the device's parent bus and all
136 child buses, and re-discover devices removed earlier
137 from this part of the device tree.
149 their ordering. Writing a space-separated list of names of
151 used when resetting the device. Writing an empty string
152 disables the ability to reset the device. Writing
161 without affecting other functions in the same device.
170 A file named vpd in a device directory will be a
172 device. It should follow the VPD format defined in
182 This symbolic link appears when hardware supports the SR-IOV
184 The symbolic link points to the PCI device sysfs entry of the
185 Virtual Function whose index is N (0...MaxVFs-1).
191 This symbolic link appears when hardware supports the SR-IOV
193 and this device has vendor specific dependencies with others.
194 The symbolic link points to the PCI device sysfs entry of
195 Physical Function this device depends on.
201 This symbolic link appears when a device is a Virtual Function.
202 The symbolic link points to the PCI device sysfs entry of the
203 Physical Function this device associates with.
207 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
209 This attribute indicates the PCI ID of the device object.
215 - vXXXXXXXX contains the vendor ID;
216 - dXXXXXXXX contains the device ID;
217 - svXXXXXXXX contains the sub-vendor ID;
218 - sdXXXXXXXX contains the subsystem device ID;
219 - bcXX contains the device class;
220 - scXX contains the device subclass;
221 - iXX contains the device class programming interface.
225 Contact: linux-pci@vger.kernel.org
232 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
236 the PCI device. The attribute will be created only
237 if the firmware has given a name to the PCI device.
242 firmware assigned name of the PCI device.
246 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
249 number of the PCI device. Depending on the platform this can
250 be for example the SMBIOS type 41 device type instance or the
251 user-defined ID (UID) on s390. The attribute will be created
253 device and that number is guaranteed to uniquely identify the
254 device in the system.
257 firmware assigned device type instance of the PCI
258 device that can help in understanding the firmware
259 intended order of the PCI device.
263 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
266 given instance (ACPI _DSM instance number) of the PCI device.
268 an instance number to the PCI device. ACPI _DSM instance number
270 type 41 device type instance also.
274 device that can help in understanding the firmware
275 intended order of the PCI device.
282 device can be put into D3Cold state. If it is cleared, the
283 device will never be put into D3Cold state. If it is set, the
284 device may be put into D3Cold state if other requirements are
293 This file appears when a physical PCIe device supports SR-IOV.
297 in the PF's SR-IOV extended capability structure's TotalVFs
306 This file appears when a physical PCIe device supports SR-IOV.
327 This file allows the driver for a device to be specified which
328 will override standard static and dynamic ID matching. When
331 device. The override is specified by writing a string to the
332 driver_override file (echo pci-stub > driver_override) and
334 This returns the device to standard matching rules binding.
336 device from its current driver or make any attempt to
338 matching name is currently loaded in the kernel, the device
340 opt-out of driver binding using a driver_override name such as
348 This file contains the NUMA node to which the PCI device is
349 attached, or -1 if the node is unknown. The initial value
361 This file contains the revision field of the PCI device.
362 The value comes from device config space. The file is read only.
368 This file is associated with the PF of a device that
369 supports SR-IOV. It determines whether newly-enabled VFs
377 VFs, then assign the newly-created VFs to virtual machines.
378 Note that changing this file does not affect already-
380 the VFs, write 0 to sriov_drivers_autoprobe, then re-enable
390 If the device has any Peer-to-Peer memory registered, this
391 file contains the total amount of memory that the device
398 If the device has any Peer-to-Peer memory registered, this
406 If the device has any Peer-to-Peer memory registered, this
408 use outside the driver that owns the device.
416 of Peer-to-Peer memory for use in Peer-to-Peer transactions.
418 files for Peer-to-Peer copies.
435 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
437 This file contains the current PCI power state of the device.
438 The value comes from the PCI kernel device state and can be one
446 This file is associated with a SR-IOV physical function (PF).
447 It contains the total number of MSI-X vectors available for
449 The value will be zero if the device doesn't support this
451 constant and won't be changed after MSI-X vectors assignment.
457 This file is associated with a SR-IOV virtual function (VF).
458 It allows configuration of the number of MSI-X vectors for
459 the VF. This allows devices that have a global pool of MSI-X
463 * > 0 - this number will be reported as the Table Size in the
464 VF's MSI-X capability
465 * < 0 - not valid
466 * = 0 - will reset to the device default value
469 implements ->sriov_set_msix_vec_count().
477 PCIe Resizable BAR extended capability of the device. Reading
485 example the device supports 64MB, 128MB, and 256MB BAR sizes.
497 be unbound from the device and peer devices under the same
500 console drivers from the device. Raw users of pci-sysfs