projects / deliverable / linux.git / blame
| Commit | Line | Data |
|---|---|---|
| d22157b3 CW |
1 | What: /sys/bus/pci/drivers/.../bind |
| 2 | Date: December 2003 | |
| 3 | Contact: linux-pci@vger.kernel.org | |
| 4 | Description: | |
| 5 | Writing a device location to this file will cause | |
| 6 | the driver to attempt to bind to the device found at | |
| 7 | this location. This is useful for overriding default | |
| 8 | bindings. The format for the location is: DDDD:BB:DD.F. | |
| 9 | That is Domain:Bus:Device.Function and is the same as | |
| 10 | found in /sys/bus/pci/devices/. For example: | |
| 11 | # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind | |
| 12 | (Note: kernels before 2.6.28 may require echo -n). | |
| 13 | ||
| 14 | What: /sys/bus/pci/drivers/.../unbind | |
| 15 | Date: December 2003 | |
| 16 | Contact: linux-pci@vger.kernel.org | |
| 17 | Description: | |
| 18 | Writing a device location to this file will cause the | |
| 19 | driver to attempt to unbind from the device found at | |
| 20 | this location. This may be useful when overriding default | |
| 21 | bindings. The format for the location is: DDDD:BB:DD.F. | |
| 22 | That is Domain:Bus:Device.Function and is the same as | |
| 23 | found in /sys/bus/pci/devices/. For example: | |
| 24 | # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind | |
| 25 | (Note: kernels before 2.6.28 may require echo -n). | |
| 26 | ||
| 27 | What: /sys/bus/pci/drivers/.../new_id | |
| 28 | Date: December 2003 | |
| 29 | Contact: linux-pci@vger.kernel.org | |
| 30 | Description: | |
| 31 | Writing a device ID to this file will attempt to | |
| 32 | dynamically add a new device ID to a PCI device driver. | |
| 33 | This may allow the driver to support more hardware than | |
| 34 | was included in the driver's static device ID support | |
| 35 | table at compile time. The format for the device ID is: | |
| 36 | VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, | |
| 37 | Device ID, Subsystem Vendor ID, Subsystem Device ID, | |
| 38 | Class, Class Mask, and Private Driver Data. The Vendor ID | |
| 39 | and Device ID fields are required, the rest are optional. | |
| 40 | Upon successfully adding an ID, the driver will probe | |
| 41 | for the device and attempt to bind to it. For example: | |
| 42 | # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id | |
| 43 | ||
| 0994375e CW |
44 | What: /sys/bus/pci/drivers/.../remove_id |
| 45 | Date: February 2009 | |
| 46 | Contact: Chris Wright <chrisw@sous-sol.org> | |
| 47 | Description: | |
| 48 | Writing a device ID to this file will remove an ID | |
| 49 | that was dynamically added via the new_id sysfs entry. | |
| 50 | The format for the device ID is: | |
| 51 | VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device | |
| 52 | ID, Subsystem Vendor ID, Subsystem Device ID, Class, | |
| 53 | and Class Mask. The Vendor ID and Device ID fields are | |
| 54 | required, the rest are optional. After successfully | |
| 55 | removing an ID, the driver will no longer support the | |
| 56 | device. This is useful to ensure auto probing won't | |
| 57 | match the driver to the device. For example: | |
| 58 | # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id | |
| 59 | ||
| 94e61088 BH |
60 | What: /sys/bus/pci/devices/.../vpd |
| 61 | Date: February 2008 | |
| 62 | Contact: Ben Hutchings <bhutchings@solarflare.com> | |
| 63 | Description: | |
| 64 | A file named vpd in a device directory will be a | |
| 65 | binary file containing the Vital Product Data for the | |
| 66 | device. It should follow the VPD format defined in | |
| 67 | PCI Specification 2.1 or 2.2, but users should consider | |
| 68 | that some devices may have malformatted data. If the | |
| 69 | underlying VPD has a writable section then the | |
| 70 | corresponding section of this file will be writable. |