Lines Matching +full:non +full:- +full:pci
1 What: /sys/bus/pci/drivers/.../bind
4 Contact: linux-pci@vger.kernel.org
11 found in /sys/bus/pci/devices/. For example::
13 # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
15 (Note: kernels before 2.6.28 may require echo -n).
17 What: /sys/bus/pci/drivers/.../unbind
20 Contact: linux-pci@vger.kernel.org
27 found in /sys/bus/pci/devices/. For example::
29 # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
31 (Note: kernels before 2.6.28 may require echo -n).
33 What: /sys/bus/pci/drivers/.../new_id
36 Contact: linux-pci@vger.kernel.org
39 dynamically add a new device ID to a PCI device driver.
50 # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
52 What: /sys/bus/pci/drivers/.../remove_id
55 Contact: Chris Wright <chrisw@sous-sol.org>
68 # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id
70 What: /sys/bus/pci/rescan
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
75 force a rescan of all PCI buses in the system, and
76 re-discover previously removed devices.
78 What: /sys/bus/pci/devices/.../msi_bus
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
88 What: /sys/bus/pci/devices/.../msi_irqs/
96 What: /sys/bus/pci/devices/.../msi_irqs/<N>
103 What: /sys/bus/pci/devices/.../irq
105 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
107 If a driver has enabled MSI (not MSI-X), "irq" contains the
114 What: /sys/bus/pci/devices/.../remove
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.
121 What: /sys/bus/pci/devices/.../pci_bus/.../rescan
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
130 What: /sys/bus/pci/devices/.../rescan
132 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
134 Writing a non-zero value to this attribute will
136 child buses, and re-discover devices removed earlier
139 What: /sys/bus/pci/devices/.../reset_method
149 their ordering. Writing a space-separated list of names of
156 What: /sys/bus/pci/devices/.../reset
166 What: /sys/bus/pci/devices/.../reset_subordinate
168 Contact: linux-pci@vger.kernel.org
177 What: /sys/bus/pci/devices/.../vpd
184 PCI Specification 2.1 or 2.2, but users should consider
189 What: /sys/bus/pci/devices/.../virtfn<N>
193 This symbolic link appears when hardware supports the SR-IOV
195 The symbolic link points to the PCI device sysfs entry of the
196 Virtual Function whose index is N (0...MaxVFs-1).
198 What: /sys/bus/pci/devices/.../dep_link
202 This symbolic link appears when hardware supports the SR-IOV
205 The symbolic link points to the PCI device sysfs entry of
208 What: /sys/bus/pci/devices/.../physfn
213 The symbolic link points to the PCI device sysfs entry of the
216 What: /sys/bus/pci/devices/.../modalias
218 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
220 This attribute indicates the PCI ID of the device object.
223 pci:vXXXXXXXXdXXXXXXXXsvXXXXXXXXsdXXXXXXXXbcXXscXXiXX,
226 - vXXXXXXXX contains the vendor ID;
227 - dXXXXXXXX contains the device ID;
228 - svXXXXXXXX contains the sub-vendor ID;
229 - sdXXXXXXXX contains the subsystem device ID;
230 - bcXX contains the device class;
231 - scXX contains the device subclass;
232 - iXX contains the device class programming interface.
234 What: /sys/bus/pci/slots/.../module
236 Contact: linux-pci@vger.kernel.org
238 This symbolic link points to the PCI hotplug controller driver
241 What: /sys/bus/pci/devices/.../label
243 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
247 the PCI device. The attribute will be created only
248 if the firmware has given a name to the PCI device.
253 firmware assigned name of the PCI device.
255 What: /sys/bus/pci/devices/.../index
257 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
260 number of the PCI device. Depending on the platform this can
262 user-defined ID (UID) on s390. The attribute will be created
263 only if the firmware has given an instance number to the PCI
268 firmware assigned device type instance of the PCI
270 intended order of the PCI device.
272 What: /sys/bus/pci/devices/.../acpi_index
274 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
277 given instance (ACPI _DSM instance number) of the PCI device.
279 an instance number to the PCI device. ACPI _DSM instance number
284 firmware assigned instance number of the PCI
286 intended order of the PCI device.
288 What: /sys/bus/pci/devices/.../d3cold_allowed
292 d3cold_allowed is bit to control whether the corresponding PCI
300 What: /sys/bus/pci/devices/.../sriov_totalvfs
304 This file appears when a physical PCIe device supports SR-IOV.
308 in the PF's SR-IOV extended capability structure's TotalVFs
313 What: /sys/bus/pci/devices/.../sriov_numvfs
317 This file appears when a physical PCIe device supports SR-IOV.
334 What: /sys/bus/pci/devices/.../driver_override
343 driver_override file (echo pci-stub > driver_override) and
351 opt-out of driver binding using a driver_override name such as
355 What: /sys/bus/pci/devices/.../numa_node
359 This file contains the NUMA node to which the PCI device is
360 attached, or -1 if the node is unknown. The initial value
368 What: /sys/bus/pci/devices/.../revision
372 This file contains the revision field of the PCI device.
375 What: /sys/bus/pci/devices/.../sriov_drivers_autoprobe
380 supports SR-IOV. It determines whether newly-enabled VFs
388 VFs, then assign the newly-created VFs to virtual machines.
389 Note that changing this file does not affect already-
391 the VFs, write 0 to sriov_drivers_autoprobe, then re-enable
394 This is similar to /sys/bus/pci/drivers_autoprobe, but
397 What: /sys/bus/pci/devices/.../p2pmem/size
401 If the device has any Peer-to-Peer memory registered, this
405 What: /sys/bus/pci/devices/.../p2pmem/available
409 If the device has any Peer-to-Peer memory registered, this
413 What: /sys/bus/pci/devices/.../p2pmem/published
417 If the device has any Peer-to-Peer memory registered, this
421 What: /sys/bus/pci/devices/.../p2pmem/allocate
427 of Peer-to-Peer memory for use in Peer-to-Peer transactions.
429 files for Peer-to-Peer copies.
431 What: /sys/bus/pci/devices/.../link/clkpm
432 /sys/bus/pci/devices/.../link/l0s_aspm
433 /sys/bus/pci/devices/.../link/l1_aspm
434 /sys/bus/pci/devices/.../link/l1_1_aspm
435 /sys/bus/pci/devices/.../link/l1_2_aspm
436 /sys/bus/pci/devices/.../link/l1_1_pcipm
437 /sys/bus/pci/devices/.../link/l1_2_pcipm
444 What: /sys/bus/pci/devices/.../power_state
446 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
448 This file contains the current PCI power state of the device.
449 The value comes from the PCI kernel device state and can be one
453 What: /sys/bus/pci/devices/.../sriov_vf_total_msix
457 This file is associated with a SR-IOV physical function (PF).
458 It contains the total number of MSI-X vectors available for
462 constant and won't be changed after MSI-X vectors assignment.
464 What: /sys/bus/pci/devices/.../sriov_vf_msix_count
468 This file is associated with a SR-IOV virtual function (VF).
469 It allows configuration of the number of MSI-X vectors for
470 the VF. This allows devices that have a global pool of MSI-X
474 * > 0 - this number will be reported as the Table Size in the
475 VF's MSI-X capability
476 * < 0 - not valid
477 * = 0 - will reset to the device default value
480 implements ->sriov_set_msix_vec_count().
482 What: /sys/bus/pci/devices/.../resourceN_resize
507 In order to make use of resource resizing, all PCI drivers must
511 console drivers from the device. Raw users of pci-sysfs
515 What: /sys/bus/pci/devices/.../leds/*:enclosure:*/brightness
523 below /sys/class/leds and below NPEM-capable PCI devices.
533 - <bdf> is the domain, bus, device and function number
535 - <indication> is a short description of the LED indication
537 Valid indications per PCIe r6.1 table 6-27 are:
539 - ok (drive is functioning normally)
540 - locate (drive is being identified by an admin)
541 - fail (drive is not functioning properly)
542 - rebuild (drive is part of an array that is rebuilding)
543 - pfa (drive is predicted to fail soon)
544 - hotspare (drive is marked to be used as a replacement)
545 - ica (drive is part of an array that is degraded)
546 - ifa (drive is part of an array that is failed)
547 - idt (drive is not the right type for the connector)
548 - disabled (drive is disabled, removal is safe)
549 - specific0 to specific7 (enclosure-specific indications)
553 - to signify drive state (ok, locate, fail, idt, disabled)
554 - to signify drive role or state in a software RAID array
556 - to signify any other role or state (specific0 to specific7)
578 PCI Firmware Specification r3.3 sec 4.7 defines a DSM interface
583 enclosure-specific indications "specific0" to "specific7",
587 What: /sys/bus/pci/devices/.../doe_features
589 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
616 What: /sys/bus/pci/devices/.../serial_number
620 This is visible only for PCI devices that support the serial