sysfs-class-devlink 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130
  1. What: /sys/class/devlink/.../
  2. Date: May 2020
  3. Contact: Saravana Kannan <[email protected]>
  4. Description:
  5. Provide a place in sysfs for the device link objects in the
  6. kernel at any given time. The name of a device link directory,
  7. denoted as ... above, is of the form <supplier>--<consumer>
  8. where <supplier> is the supplier bus:device name and <consumer>
  9. is the consumer bus:device name.
  10. What: /sys/class/devlink/.../auto_remove_on
  11. Date: May 2020
  12. Contact: Saravana Kannan <[email protected]>
  13. Description:
  14. This file indicates if the device link will ever be
  15. automatically removed by the driver core when the consumer and
  16. supplier devices themselves are still present.
  17. This will be one of the following strings:
  18. - 'consumer unbind'
  19. - 'supplier unbind'
  20. - 'never'
  21. 'consumer unbind' means the device link will be removed when
  22. the consumer's driver is unbound from the consumer device.
  23. 'supplier unbind' means the device link will be removed when
  24. the supplier's driver is unbound from the supplier device.
  25. 'never' means the device link will not be automatically removed
  26. when as long as the supplier and consumer devices themselves
  27. are still present.
  28. What: /sys/class/devlink/.../consumer
  29. Date: May 2020
  30. Contact: Saravana Kannan <[email protected]>
  31. Description:
  32. This file is a symlink to the consumer device's sysfs directory.
  33. What: /sys/class/devlink/.../runtime_pm
  34. Date: May 2020
  35. Contact: Saravana Kannan <[email protected]>
  36. Description:
  37. This file indicates if the device link has any impact on the
  38. runtime power management behavior of the consumer and supplier
  39. devices. For example: Making sure the supplier doesn't enter
  40. runtime suspend while the consumer is active.
  41. This will be one of the following strings:
  42. === ========================================
  43. '0' Does not affect runtime power management
  44. '1' Affects runtime power management
  45. === ========================================
  46. What: /sys/class/devlink/.../status
  47. Date: May 2020
  48. Contact: Saravana Kannan <[email protected]>
  49. Description:
  50. This file indicates the status of the device link. The status
  51. of a device link is affected by whether the supplier and
  52. consumer devices have been bound to their corresponding
  53. drivers. The status of a device link also affects the binding
  54. and unbinding of the supplier and consumer devices with their
  55. drivers and also affects whether the software state of the
  56. supplier device is synced with the hardware state of the
  57. supplier device after boot up.
  58. See also: sysfs-devices-state_synced.
  59. This will be one of the following strings:
  60. - 'not tracked'
  61. - 'dormant'
  62. - 'available'
  63. - 'consumer probing'
  64. - 'active'
  65. - 'supplier unbinding'
  66. - 'unknown'
  67. 'not tracked' means this device link does not track the status
  68. and has no impact on the binding, unbinding and syncing the
  69. hardware and software device state.
  70. 'dormant' means the supplier and the consumer devices have not
  71. bound to their driver.
  72. 'available' means the supplier has bound to its driver and is
  73. available to supply resources to the consumer device.
  74. 'consumer probing' means the consumer device is currently
  75. trying to bind to its driver.
  76. 'active' means the supplier and consumer devices have both
  77. bound successfully to their drivers.
  78. 'supplier unbinding' means the supplier devices is currently in
  79. the process of unbinding from its driver.
  80. 'unknown' means the state of the device link is not any of the
  81. above. If this is ever the value, there's a bug in the kernel.
  82. What: /sys/class/devlink/.../supplier
  83. Date: May 2020
  84. Contact: Saravana Kannan <[email protected]>
  85. Description:
  86. This file is a symlink to the supplier device's sysfs directory.
  87. What: /sys/class/devlink/.../sync_state_only
  88. Date: May 2020
  89. Contact: Saravana Kannan <[email protected]>
  90. Description:
  91. This file indicates if the device link is limited to only
  92. affecting the syncing of the hardware and software state of the
  93. supplier device.
  94. This will be one of the following strings:
  95. === ================================
  96. '0'
  97. '1' Affects runtime power management
  98. === ================================
  99. '0' means the device link can affect other device behaviors
  100. like binding/unbinding, suspend/resume, runtime power
  101. management, etc.
  102. '1' means the device link will only affect the syncing of
  103. hardware and software state of the supplier device after boot
  104. up and doesn't not affect other behaviors of the devices.