1 What: /sys/kernel/debug/habanalabs/hl<n>/addr
4 Contact: oded.gabbay@gmail.com
5 Description: Sets the device address to be used for read or write through
6 PCI bar. The acceptable value is a string that starts with "0x"
8 What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
11 Contact: oded.gabbay@gmail.com
12 Description: Displays a list with information about the currently allocated
15 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
18 Contact: oded.gabbay@gmail.com
19 Description: Displays a list with information about the currently active
22 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
25 Contact: oded.gabbay@gmail.com
26 Description: Displays a list with detailed information about each JOB (CB) of
27 each active command submission
29 What: /sys/kernel/debug/habanalabs/hl<n>/data32
32 Contact: oded.gabbay@gmail.com
33 Description: Allows the root user to read or write directly through the
34 device's PCI bar. Writing to this file generates a write
35 transaction while reading from the file generates a read
36 transcation. This custom interface is needed (instead of using
37 the generic Linux user-space PCI mapping) because the DDR bar
38 is very small compared to the DDR memory and only the driver can
39 move the bar before and after the transaction
41 What: /sys/kernel/debug/habanalabs/hl<n>/device
44 Contact: oded.gabbay@gmail.com
45 Description: Enables the root user to set the device to specific state.
46 Valid values are "disable", "enable", "suspend", "resume".
47 User can read this property to see the valid values
49 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_addr
52 Contact: oded.gabbay@gmail.com
53 Description: Sets I2C device address for I2C transaction that is generated
56 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_bus
59 Contact: oded.gabbay@gmail.com
60 Description: Sets I2C bus address for I2C transaction that is generated by
63 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_data
66 Contact: oded.gabbay@gmail.com
67 Description: Triggers an I2C transaction that is generated by the device's
68 CPU. Writing to this file generates a write transaction while
69 reading from the file generates a read transcation
71 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_reg
74 Contact: oded.gabbay@gmail.com
75 Description: Sets I2C register id for I2C transaction that is generated by
78 What: /sys/kernel/debug/habanalabs/hl<n>/led0
81 Contact: oded.gabbay@gmail.com
82 Description: Sets the state of the first S/W led on the device
84 What: /sys/kernel/debug/habanalabs/hl<n>/led1
87 Contact: oded.gabbay@gmail.com
88 Description: Sets the state of the second S/W led on the device
90 What: /sys/kernel/debug/habanalabs/hl<n>/led2
93 Contact: oded.gabbay@gmail.com
94 Description: Sets the state of the third S/W led on the device
96 What: /sys/kernel/debug/habanalabs/hl<n>/mmu
99 Contact: oded.gabbay@gmail.com
100 Description: Displays the hop values and physical address for a given ASID
101 and virtual address. The user should write the ASID and VA into
102 the file and then read the file to get the result.
103 e.g. to display info about VA 0x1000 for ASID 1 you need to do:
104 echo "1 0x1000" > /sys/kernel/debug/habanalabs/hl0/mmu
106 What: /sys/kernel/debug/habanalabs/hl<n>/set_power_state
109 Contact: oded.gabbay@gmail.com
110 Description: Sets the PCI power state. Valid values are "1" for D0 and "2"
113 What: /sys/kernel/debug/habanalabs/hl<n>/userptr
116 Contact: oded.gabbay@gmail.com
117 Description: Displays a list with information about the currently user
118 pointers (user virtual addresses) that are pinned and mapped
121 What: /sys/kernel/debug/habanalabs/hl<n>/vm
124 Contact: oded.gabbay@gmail.com
125 Description: Displays a list with information about all the active virtual
126 address mappings per ASID