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.
168 Contact: linux-pci@vger.kernel.org
172 bridge device, writing 1 to this will try to do it. This will
181 A file named vpd in a device directory will be a
183 device. It should follow the VPD format defined in
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).
202 This symbolic link appears when hardware supports the SR-IOV
204 and this device has vendor specific dependencies with others.
205 The symbolic link points to the PCI device sysfs entry of
206 Physical Function this device depends on.
212 This symbolic link appears when a device is a Virtual Function.
213 The symbolic link points to the PCI device sysfs entry of the
214 Physical Function this device associates with.
218 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
220 This attribute indicates the PCI ID of the device object.
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-pci@vger.kernel.org
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.
257 Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
260 number of the PCI device. Depending on the platform this can
261 be for example the SMBIOS type 41 device type instance or the
262 user-defined ID (UID) on s390. The attribute will be created
264 device and that number is guaranteed to uniquely identify the
265 device in the system.
268 firmware assigned device type instance of the PCI
269 device that can help in understanding the firmware
270 intended order of the PCI device.
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
281 type 41 device type instance also.
285 device that can help in understanding the firmware
286 intended order of the PCI device.
293 device can be put into D3Cold state. If it is cleared, the
294 device will never be put into D3Cold state. If it is set, the
295 device may be put into D3Cold state if other requirements are
304 This file appears when a physical PCIe device supports SR-IOV.
308 in the PF's SR-IOV extended capability structure's TotalVFs
317 This file appears when a physical PCIe device supports SR-IOV.
338 This file allows the driver for a device to be specified which
339 will override standard static and dynamic ID matching. When
342 device. The override is specified by writing a string to the
343 driver_override file (echo pci-stub > driver_override) and
345 This returns the device to standard matching rules binding.
347 device from its current driver or make any attempt to
349 matching name is currently loaded in the kernel, the device
351 opt-out of driver binding using a driver_override name such as
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
372 This file contains the revision field of the PCI device.
373 The value comes from device config space. The file is read only.
379 This file is associated with the PF of a device that
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
402 file contains the total amount of memory that the device
409 If the device has any Peer-to-Peer memory registered, this
417 If the device has any Peer-to-Peer memory registered, this
419 use outside the driver that owns the device.
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-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
457 This file is associated with a SR-IOV physical function (PF).
458 It contains the total number of MSI-X vectors available for
460 The value will be zero if the device doesn't support this
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().
488 PCIe Resizable BAR extended capability of the device. Reading
496 example the device supports 64MB, 128MB, and 256MB BAR sizes.
508 be unbound from the device and peer devices under the same
511 console drivers from the device. Raw users of pci-sysfs
523 below /sys/class/leds and below NPEM-capable PCI devices.
529 The name of a led class device is as follows:
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)
560 A led class device is only visible if the corresponding
561 indication is supported by the device.
580 firmware to a device's NPEM registers. The kernel will use
583 enclosure-specific indications "specific0" to "specific7",