1What:           /sys/kernel/debug/habanalabs/hl<n>/addr
2Date:           Jan 2019
3KernelVersion:  5.1
4Contact:        oded.gabbay@gmail.com
5Description:    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
11What:           /sys/kernel/debug/habanalabs/hl<n>/command_buffers
12Date:           Jan 2019
13KernelVersion:  5.1
14Contact:        oded.gabbay@gmail.com
15Description:    Displays a list with information about the currently allocated
16                command buffers
17
18What:           /sys/kernel/debug/habanalabs/hl<n>/command_submission
19Date:           Jan 2019
20KernelVersion:  5.1
21Contact:        oded.gabbay@gmail.com
22Description:    Displays a list with information about the currently active
23                command submissions
24
25What:           /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
26Date:           Jan 2019
27KernelVersion:  5.1
28Contact:        oded.gabbay@gmail.com
29Description:    Displays a list with detailed information about each JOB (CB) of
30                each active command submission
31
32What:           /sys/kernel/debug/habanalabs/hl<n>/data32
33Date:           Jan 2019
34KernelVersion:  5.1
35Contact:        oded.gabbay@gmail.com
36Description:    Allows the root user to read or write directly through the
37                device's PCI bar. Writing to this file generates a write
38                transaction while reading from the file generates a read
39                transaction. This custom interface is needed (instead of using
40                the generic Linux user-space PCI mapping) because the DDR bar
41                is very small compared to the DDR memory and only the driver can
42                move the bar before and after the transaction.
43                If the IOMMU is disabled, it also allows the root user to read
44                or write from the host a device VA of a host mapped memory
45
46What:           /sys/kernel/debug/habanalabs/hl<n>/device
47Date:           Jan 2019
48KernelVersion:  5.1
49Contact:        oded.gabbay@gmail.com
50Description:    Enables the root user to set the device to specific state.
51                Valid values are "disable", "enable", "suspend", "resume".
52                User can read this property to see the valid values
53
54What:           /sys/kernel/debug/habanalabs/hl<n>/engines
55Date:           Jul 2019
56KernelVersion:  5.3
57Contact:        oded.gabbay@gmail.com
58Description:    Displays the status registers values of the device engines and
59                their derived idle status
60
61What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_addr
62Date:           Jan 2019
63KernelVersion:  5.1
64Contact:        oded.gabbay@gmail.com
65Description:    Sets I2C device address for I2C transaction that is generated
66                by the device's CPU
67
68What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_bus
69Date:           Jan 2019
70KernelVersion:  5.1
71Contact:        oded.gabbay@gmail.com
72Description:    Sets I2C bus address for I2C transaction that is generated by
73                the device's CPU
74
75What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_data
76Date:           Jan 2019
77KernelVersion:  5.1
78Contact:        oded.gabbay@gmail.com
79Description:    Triggers an I2C transaction that is generated by the device's
80                CPU. Writing to this file generates a write transaction while
81                reading from the file generates a read transcation
82
83What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_reg
84Date:           Jan 2019
85KernelVersion:  5.1
86Contact:        oded.gabbay@gmail.com
87Description:    Sets I2C register id for I2C transaction that is generated by
88                the device's CPU
89
90What:           /sys/kernel/debug/habanalabs/hl<n>/led0
91Date:           Jan 2019
92KernelVersion:  5.1
93Contact:        oded.gabbay@gmail.com
94Description:    Sets the state of the first S/W led on the device
95
96What:           /sys/kernel/debug/habanalabs/hl<n>/led1
97Date:           Jan 2019
98KernelVersion:  5.1
99Contact:        oded.gabbay@gmail.com
100Description:    Sets the state of the second S/W led on the device
101
102What:           /sys/kernel/debug/habanalabs/hl<n>/led2
103Date:           Jan 2019
104KernelVersion:  5.1
105Contact:        oded.gabbay@gmail.com
106Description:    Sets the state of the third S/W led on the device
107
108What:           /sys/kernel/debug/habanalabs/hl<n>/mmu
109Date:           Jan 2019
110KernelVersion:  5.1
111Contact:        oded.gabbay@gmail.com
112Description:    Displays the hop values and physical address for a given ASID
113                and virtual address. The user should write the ASID and VA into
114                the file and then read the file to get the result.
115                e.g. to display info about VA 0x1000 for ASID 1 you need to do:
116                echo "1 0x1000" > /sys/kernel/debug/habanalabs/hl0/mmu
117
118What:           /sys/kernel/debug/habanalabs/hl<n>/set_power_state
119Date:           Jan 2019
120KernelVersion:  5.1
121Contact:        oded.gabbay@gmail.com
122Description:    Sets the PCI power state. Valid values are "1" for D0 and "2"
123                for D3Hot
124
125What:           /sys/kernel/debug/habanalabs/hl<n>/userptr
126Date:           Jan 2019
127KernelVersion:  5.1
128Contact:        oded.gabbay@gmail.com
129Description:    Displays a list with information about the currently user
130                pointers (user virtual addresses) that are pinned and mapped
131                to DMA addresses
132
133What:           /sys/kernel/debug/habanalabs/hl<n>/vm
134Date:           Jan 2019
135KernelVersion:  5.1
136Contact:        oded.gabbay@gmail.com
137Description:    Displays a list with information about all the active virtual
138                address mappings per ASID
139