debugfs-driver-habanalabs 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  1. What: /sys/kernel/debug/habanalabs/hl<n>/addr
  2. Date: Jan 2019
  3. KernelVersion: 5.1
  4. Contact: oded.gabbay@gmail.com
  5. Description: Sets the device address to be used for read or write through
  6. PCI bar, or the device VA of a host mapped memory to be read or
  7. written directly from the host. The latter option is allowed
  8. only when the IOMMU is disabled.
  9. The acceptable value is a string that starts with "0x"
  10. What: /sys/kernel/debug/habanalabs/hl<n>/clk_gate
  11. Date: May 2020
  12. KernelVersion: 5.8
  13. Contact: oded.gabbay@gmail.com
  14. Description: Allow the root user to disable/enable in runtime the clock
  15. gating mechanism in Gaudi. Due to how Gaudi is built, the
  16. clock gating needs to be disabled in order to access the
  17. registers of the TPC and MME engines. This is sometimes needed
  18. during debug by the user and hence the user needs this option.
  19. The user can supply a bitmask value, each bit represents
  20. a different engine to disable/enable its clock gating feature.
  21. The bitmask is composed of 20 bits:
  22. ======= ============
  23. 0 - 7 DMA channels
  24. 8 - 11 MME engines
  25. 12 - 19 TPC engines
  26. ======= ============
  27. The bit's location of a specific engine can be determined
  28. using (1 << GAUDI_ENGINE_ID_*). GAUDI_ENGINE_ID_* values
  29. are defined in uapi habanalabs.h file in enum gaudi_engine_id
  30. What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
  31. Date: Jan 2019
  32. KernelVersion: 5.1
  33. Contact: oded.gabbay@gmail.com
  34. Description: Displays a list with information about the currently allocated
  35. command buffers
  36. What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
  37. Date: Jan 2019
  38. KernelVersion: 5.1
  39. Contact: oded.gabbay@gmail.com
  40. Description: Displays a list with information about the currently active
  41. command submissions
  42. What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
  43. Date: Jan 2019
  44. KernelVersion: 5.1
  45. Contact: oded.gabbay@gmail.com
  46. Description: Displays a list with detailed information about each JOB (CB) of
  47. each active command submission
  48. What: /sys/kernel/debug/habanalabs/hl<n>/data32
  49. Date: Jan 2019
  50. KernelVersion: 5.1
  51. Contact: oded.gabbay@gmail.com
  52. Description: Allows the root user to read or write directly through the
  53. device's PCI bar. Writing to this file generates a write
  54. transaction while reading from the file generates a read
  55. transaction. This custom interface is needed (instead of using
  56. the generic Linux user-space PCI mapping) because the DDR bar
  57. is very small compared to the DDR memory and only the driver can
  58. move the bar before and after the transaction.
  59. If the IOMMU is disabled, it also allows the root user to read
  60. or write from the host a device VA of a host mapped memory
  61. What: /sys/kernel/debug/habanalabs/hl<n>/data64
  62. Date: Jan 2020
  63. KernelVersion: 5.6
  64. Contact: oded.gabbay@gmail.com
  65. Description: Allows the root user to read or write 64 bit data directly
  66. through the device's PCI bar. Writing to this file generates a
  67. write transaction while reading from the file generates a read
  68. transaction. This custom interface is needed (instead of using
  69. the generic Linux user-space PCI mapping) because the DDR bar
  70. is very small compared to the DDR memory and only the driver can
  71. move the bar before and after the transaction.
  72. If the IOMMU is disabled, it also allows the root user to read
  73. or write from the host a device VA of a host mapped memory
  74. What: /sys/kernel/debug/habanalabs/hl<n>/device
  75. Date: Jan 2019
  76. KernelVersion: 5.1
  77. Contact: oded.gabbay@gmail.com
  78. Description: Enables the root user to set the device to specific state.
  79. Valid values are "disable", "enable", "suspend", "resume".
  80. User can read this property to see the valid values
  81. What: /sys/kernel/debug/habanalabs/hl<n>/engines
  82. Date: Jul 2019
  83. KernelVersion: 5.3
  84. Contact: oded.gabbay@gmail.com
  85. Description: Displays the status registers values of the device engines and
  86. their derived idle status
  87. What: /sys/kernel/debug/habanalabs/hl<n>/i2c_addr
  88. Date: Jan 2019
  89. KernelVersion: 5.1
  90. Contact: oded.gabbay@gmail.com
  91. Description: Sets I2C device address for I2C transaction that is generated
  92. by the device's CPU
  93. What: /sys/kernel/debug/habanalabs/hl<n>/i2c_bus
  94. Date: Jan 2019
  95. KernelVersion: 5.1
  96. Contact: oded.gabbay@gmail.com
  97. Description: Sets I2C bus address for I2C transaction that is generated by
  98. the device's CPU
  99. What: /sys/kernel/debug/habanalabs/hl<n>/i2c_data
  100. Date: Jan 2019
  101. KernelVersion: 5.1
  102. Contact: oded.gabbay@gmail.com
  103. Description: Triggers an I2C transaction that is generated by the device's
  104. CPU. Writing to this file generates a write transaction while
  105. reading from the file generates a read transcation
  106. What: /sys/kernel/debug/habanalabs/hl<n>/i2c_reg
  107. Date: Jan 2019
  108. KernelVersion: 5.1
  109. Contact: oded.gabbay@gmail.com
  110. Description: Sets I2C register id for I2C transaction that is generated by
  111. the device's CPU
  112. What: /sys/kernel/debug/habanalabs/hl<n>/led0
  113. Date: Jan 2019
  114. KernelVersion: 5.1
  115. Contact: oded.gabbay@gmail.com
  116. Description: Sets the state of the first S/W led on the device
  117. What: /sys/kernel/debug/habanalabs/hl<n>/led1
  118. Date: Jan 2019
  119. KernelVersion: 5.1
  120. Contact: oded.gabbay@gmail.com
  121. Description: Sets the state of the second S/W led on the device
  122. What: /sys/kernel/debug/habanalabs/hl<n>/led2
  123. Date: Jan 2019
  124. KernelVersion: 5.1
  125. Contact: oded.gabbay@gmail.com
  126. Description: Sets the state of the third S/W led on the device
  127. What: /sys/kernel/debug/habanalabs/hl<n>/mmu
  128. Date: Jan 2019
  129. KernelVersion: 5.1
  130. Contact: oded.gabbay@gmail.com
  131. Description: Displays the hop values and physical address for a given ASID
  132. and virtual address. The user should write the ASID and VA into
  133. the file and then read the file to get the result.
  134. e.g. to display info about VA 0x1000 for ASID 1 you need to do:
  135. echo "1 0x1000" > /sys/kernel/debug/habanalabs/hl0/mmu
  136. What: /sys/kernel/debug/habanalabs/hl<n>/set_power_state
  137. Date: Jan 2019
  138. KernelVersion: 5.1
  139. Contact: oded.gabbay@gmail.com
  140. Description: Sets the PCI power state. Valid values are "1" for D0 and "2"
  141. for D3Hot
  142. What: /sys/kernel/debug/habanalabs/hl<n>/userptr
  143. Date: Jan 2019
  144. KernelVersion: 5.1
  145. Contact: oded.gabbay@gmail.com
  146. Description: Displays a list with information about the currently user
  147. pointers (user virtual addresses) that are pinned and mapped
  148. to DMA addresses
  149. What: /sys/kernel/debug/habanalabs/hl<n>/vm
  150. Date: Jan 2019
  151. KernelVersion: 5.1
  152. Contact: oded.gabbay@gmail.com
  153. Description: Displays a list with information about all the active virtual
  154. address mappings per ASID
  155. What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err
  156. Date: Mar 2020
  157. KernelVersion: 5.6
  158. Contact: oded.gabbay@gmail.com
  159. Description: Sets the stop-on_error option for the device engines. Value of
  160. "0" is for disable, otherwise enable.