diff options
Diffstat (limited to 'Documentation/ABI')
| -rw-r--r-- | Documentation/ABI/testing/sysfs-bus-pci | 43 | ||||
| -rw-r--r-- | Documentation/ABI/testing/sysfs-firmware-memmap | 2 |
2 files changed, 44 insertions, 1 deletions
diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci index ceddcff4082a..e638e15a8895 100644 --- a/Documentation/ABI/testing/sysfs-bus-pci +++ b/Documentation/ABI/testing/sysfs-bus-pci | |||
| @@ -1,3 +1,46 @@ | |||
| 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 | |||
| 1 | What: /sys/bus/pci/devices/.../vpd | 44 | What: /sys/bus/pci/devices/.../vpd |
| 2 | Date: February 2008 | 45 | Date: February 2008 |
| 3 | Contact: Ben Hutchings <bhutchings@solarflare.com> | 46 | Contact: Ben Hutchings <bhutchings@solarflare.com> |
diff --git a/Documentation/ABI/testing/sysfs-firmware-memmap b/Documentation/ABI/testing/sysfs-firmware-memmap index 0d99ee6ae02e..eca0d65087dc 100644 --- a/Documentation/ABI/testing/sysfs-firmware-memmap +++ b/Documentation/ABI/testing/sysfs-firmware-memmap | |||
| @@ -1,6 +1,6 @@ | |||
| 1 | What: /sys/firmware/memmap/ | 1 | What: /sys/firmware/memmap/ |
| 2 | Date: June 2008 | 2 | Date: June 2008 |
| 3 | Contact: Bernhard Walle <bwalle@suse.de> | 3 | Contact: Bernhard Walle <bernhard.walle@gmx.de> |
| 4 | Description: | 4 | Description: |
| 5 | On all platforms, the firmware provides a memory map which the | 5 | On all platforms, the firmware provides a memory map which the |
| 6 | kernel reads. The resources from that memory map are registered | 6 | kernel reads. The resources from that memory map are registered |