Lines Matching +full:pcie +full:- +full:attached
4 Contact: linux-[email protected]
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-[email protected]
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-[email protected]
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-[email protected]>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-[email protected]>
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
105 Contact: Linux PCI developers <linux-[email protected]>
107 If a driver has enabled MSI (not MSI-X), "irq" contains the
116 Contact: Linux PCI developers <linux-[email protected]>
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-[email protected]>
125 Writing a non-zero value to this attribute will
127 and re-discover devices removed earlier from this
132 Contact: Linux PCI developers <linux-[email protected]>
134 Writing a non-zero value to this attribute will
136 child buses, and re-discover devices removed earlier
149 their ordering. Writing a space-separated list of names of
168 Contact: linux-[email protected]
171 all devices attached through the subordinate bus of a specific
173 affect all devices attached to the system through this bridge
193 This symbolic link appears when hardware supports the SR-IOV
196 Virtual Function whose index is N (0...MaxVFs-1).
202 This symbolic link appears when hardware supports the SR-IOV
218 Contact: Greg Kroah-Hartman <[email protected]>
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.
236 Contact: linux-[email protected]
243 Contact: Narendra K <[email protected]>, linux-[email protected]
257 Contact: Narendra K <[email protected]>, linux-[email protected]
262 user-defined ID (UID) on s390. The attribute will be created
274 Contact: Narendra K <[email protected]>, linux-[email protected]
304 This file appears when a physical PCIe device supports SR-IOV.
306 maximum number of Virtual Functions (VFs) a PCIe physical
308 in the PF's SR-IOV extended capability structure's TotalVFs
317 This file appears when a physical PCIe device supports SR-IOV.
343 driver_override file (echo pci-stub > driver_override) and
351 opt-out of driver binding using a driver_override name such as
360 attached, or -1 if the node is unknown. The initial value
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
401 If the device has any Peer-to-Peer memory registered, this
409 If the device has any Peer-to-Peer memory registered, this
417 If the device has any Peer-to-Peer memory registered, this
427 of Peer-to-Peer memory for use in Peer-to-Peer transactions.
429 files for Peer-to-Peer copies.
446 Contact: Linux PCI developers <linux-[email protected]>
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.
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().
486 These files provide an interface to PCIe Resizable BAR support.
488 PCIe Resizable BAR extended capability of the device. Reading
505 matches the PCIe specification of this capability.
511 console drivers from the device. Raw users of pci-sysfs
520 LED indications on PCIe storage enclosures which are controlled
521 through the NPEM interface (Native PCIe Enclosure Management,
522 PCIe r6.1 sec 6.28) are accessible as led class devices, both
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)
558 Mandatory indications per PCIe r6.1 sec 7.9.19.2 comprise:
571 The PCIe Base Specification allows vendors leeway to choose
583 enclosure-specific indications "specific0" to "specific7",