1*d22157b3SChris WrightWhat: /sys/bus/pci/drivers/.../bind 2*d22157b3SChris WrightDate: December 2003 3*d22157b3SChris WrightContact: linux-pci@vger.kernel.org 4*d22157b3SChris WrightDescription: 5*d22157b3SChris Wright Writing a device location to this file will cause 6*d22157b3SChris Wright the driver to attempt to bind to the device found at 7*d22157b3SChris Wright this location. This is useful for overriding default 8*d22157b3SChris Wright bindings. The format for the location is: DDDD:BB:DD.F. 9*d22157b3SChris Wright That is Domain:Bus:Device.Function and is the same as 10*d22157b3SChris Wright found in /sys/bus/pci/devices/. For example: 11*d22157b3SChris Wright # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind 12*d22157b3SChris Wright (Note: kernels before 2.6.28 may require echo -n). 13*d22157b3SChris Wright 14*d22157b3SChris WrightWhat: /sys/bus/pci/drivers/.../unbind 15*d22157b3SChris WrightDate: December 2003 16*d22157b3SChris WrightContact: linux-pci@vger.kernel.org 17*d22157b3SChris WrightDescription: 18*d22157b3SChris Wright Writing a device location to this file will cause the 19*d22157b3SChris Wright driver to attempt to unbind from the device found at 20*d22157b3SChris Wright this location. This may be useful when overriding default 21*d22157b3SChris Wright bindings. The format for the location is: DDDD:BB:DD.F. 22*d22157b3SChris Wright That is Domain:Bus:Device.Function and is the same as 23*d22157b3SChris Wright found in /sys/bus/pci/devices/. For example: 24*d22157b3SChris Wright # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind 25*d22157b3SChris Wright (Note: kernels before 2.6.28 may require echo -n). 26*d22157b3SChris Wright 27*d22157b3SChris WrightWhat: /sys/bus/pci/drivers/.../new_id 28*d22157b3SChris WrightDate: December 2003 29*d22157b3SChris WrightContact: linux-pci@vger.kernel.org 30*d22157b3SChris WrightDescription: 31*d22157b3SChris Wright Writing a device ID to this file will attempt to 32*d22157b3SChris Wright dynamically add a new device ID to a PCI device driver. 33*d22157b3SChris Wright This may allow the driver to support more hardware than 34*d22157b3SChris Wright was included in the driver's static device ID support 35*d22157b3SChris Wright table at compile time. The format for the device ID is: 36*d22157b3SChris Wright VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, 37*d22157b3SChris Wright Device ID, Subsystem Vendor ID, Subsystem Device ID, 38*d22157b3SChris Wright Class, Class Mask, and Private Driver Data. The Vendor ID 39*d22157b3SChris Wright and Device ID fields are required, the rest are optional. 40*d22157b3SChris Wright Upon successfully adding an ID, the driver will probe 41*d22157b3SChris Wright for the device and attempt to bind to it. For example: 42*d22157b3SChris Wright # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id 43*d22157b3SChris Wright 4494e61088SBen HutchingsWhat: /sys/bus/pci/devices/.../vpd 4594e61088SBen HutchingsDate: February 2008 4694e61088SBen HutchingsContact: Ben Hutchings <bhutchings@solarflare.com> 4794e61088SBen HutchingsDescription: 4894e61088SBen Hutchings A file named vpd in a device directory will be a 4994e61088SBen Hutchings binary file containing the Vital Product Data for the 5094e61088SBen Hutchings device. It should follow the VPD format defined in 5194e61088SBen Hutchings PCI Specification 2.1 or 2.2, but users should consider 5294e61088SBen Hutchings that some devices may have malformatted data. If the 5394e61088SBen Hutchings underlying VPD has a writable section then the 5494e61088SBen Hutchings corresponding section of this file will be writable. 55