Lines Matching +full:firmware +full:- +full:reset
3 Contact: linux-pci@vger.kernel.org
14 (Note: kernels before 2.6.28 may require echo -n).
18 Contact: linux-pci@vger.kernel.org
29 (Note: kernels before 2.6.28 may require echo -n).
33 Contact: linux-pci@vger.kernel.org
51 Contact: Chris Wright <chrisw@sous-sol.org>
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
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
117 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
119 Writing a non-zero value to this attribute will
121 child buses, and re-discover devices removed earlier
128 Some devices allow an individual function to be reset
133 gives names of the supported and enabled reset methods and
134 their ordering. Writing a space-separated list of names of
135 reset methods sets the reset methods and ordering to be
137 disables the ability to reset the device. Writing
138 "default" enables all supported reset methods in the
141 What: /sys/bus/pci/devices/.../reset
145 Some devices allow an individual function to be reset
147 For devices that have this support, a file named reset
149 will perform reset.
167 This symbolic link appears when hardware supports the SR-IOV
170 Virtual Function whose index is N (0...MaxVFs-1).
176 This symbolic link appears when hardware supports the SR-IOV
192 Contact: linux-pci@vger.kernel.org
199 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
201 Reading this attribute will provide the firmware
204 if the firmware has given a name to the PCI device.
206 system firmware provides SMBIOS type 41 string also.
209 firmware assigned name of the PCI device.
213 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
215 Reading this attribute will provide the firmware given instance
218 user-defined ID (UID) on s390. The attribute will be created
219 only if the firmware has given an instance number to the PCI
224 firmware assigned device type instance of the PCI
225 device that can help in understanding the firmware
230 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
232 Reading this attribute will provide the firmware
234 The attribute will be created only if the firmware has given
236 will be given priority if the system firmware provides SMBIOS
240 firmware assigned instance number of the PCI
241 device that can help in understanding the firmware
260 This file appears when a physical PCIe device supports SR-IOV.
264 in the PF's SR-IOV extended capability structure's TotalVFs
273 This file appears when a physical PCIe device supports SR-IOV.
299 driver_override file (echo pci-stub > driver_override) and
307 opt-out of driver binding using a driver_override name such as
316 attached, or -1 if the node is unknown. The initial value
317 comes from an ACPI _PXM method or a similar firmware
320 a firmware bug to the system vendor. Writing to this file
336 supports SR-IOV. It determines whether newly-enabled VFs
344 VFs, then assign the newly-created VFs to virtual machines.
345 Note that changing this file does not affect already-
347 the VFs, write 0 to sriov_drivers_autoprobe, then re-enable
357 If the device has any Peer-to-Peer memory registered, this
365 If the device has any Peer-to-Peer memory registered, this
373 If the device has any Peer-to-Peer memory registered, this
392 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
403 This file is associated with a SR-IOV physical function (PF).
404 It contains the total number of MSI-X vectors available for
408 constant and won't be changed after MSI-X vectors assignment.
414 This file is associated with a SR-IOV virtual function (VF).
415 It allows configuration of the number of MSI-X vectors for
416 the VF. This allows devices that have a global pool of MSI-X
420 * > 0 - this number will be reported as the Table Size in the
421 VF's MSI-X capability
422 * < 0 - not valid
423 * = 0 - will reset to the device default value
426 implements ->sriov_set_msix_vec_count().