sysfs-bus-platform 2.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. What: /sys/bus/platform/devices/.../driver_override
  2. Date: April 2014
  3. Contact: Kim Phillips <[email protected]>
  4. Description:
  5. This file allows the driver for a device to be specified which
  6. will override standard OF, ACPI, ID table, and name matching.
  7. When specified, only a driver with a name matching the value
  8. written to driver_override will have an opportunity to bind
  9. to the device. The override is specified by writing a string
  10. to the driver_override file (echo vfio-platform > \
  11. driver_override) and may be cleared with an empty string
  12. (echo > driver_override). This returns the device to standard
  13. matching rules binding. Writing to driver_override does not
  14. automatically unbind the device from its current driver or make
  15. any attempt to automatically load the specified driver. If no
  16. driver with a matching name is currently loaded in the kernel,
  17. the device will not bind to any driver. This also allows
  18. devices to opt-out of driver binding using a driver_override
  19. name such as "none". Only a single driver may be specified in
  20. the override, there is no support for parsing delimiters.
  21. What: /sys/bus/platform/devices/.../numa_node
  22. Date: June 2020
  23. Contact: Barry Song <[email protected]>
  24. Description:
  25. This file contains the NUMA node to which the platform device
  26. is attached. It won't be visible if the node is unknown. The
  27. value comes from an ACPI _PXM method or a similar firmware
  28. source. Initial users for this file would be devices like
  29. arm smmu which are populated by arm64 acpi_iort.
  30. What: /sys/bus/platform/devices/.../msi_irqs/
  31. Date: August 2021
  32. Contact: Barry Song <[email protected]>
  33. Description:
  34. The /sys/devices/.../msi_irqs directory contains a variable set
  35. of files, with each file being named after a corresponding msi
  36. irq vector allocated to that device.
  37. What: /sys/bus/platform/devices/.../msi_irqs/<N>
  38. Date: August 2021
  39. Contact: Barry Song <[email protected]>
  40. Description:
  41. This attribute will show "msi" if <N> is a valid msi irq
  42. What: /sys/bus/platform/devices/.../modalias
  43. Description:
  44. Same as MODALIAS in the uevent at device creation.
  45. A platform device that it is exposed via devicetree uses:
  46. - of:N`of node name`T`type`
  47. Other platform devices use, instead:
  48. - platform:`driver name`