1What:           /sys/class/uacce/<dev_name>/api
2Date:           Feb 2020
3KernelVersion:  5.7
4Contact:        linux-accelerators@lists.ozlabs.org
5Description:    Api of the device
6                Can be any string and up to userspace to parse.
7                Application use the api to match the correct driver
8
9What:           /sys/class/uacce/<dev_name>/flags
10Date:           Feb 2020
11KernelVersion:  5.7
12Contact:        linux-accelerators@lists.ozlabs.org
13Description:    Attributes of the device, see UACCE_DEV_xxx flag defined in uacce.h
14
15What:           /sys/class/uacce/<dev_name>/available_instances
16Date:           Feb 2020
17KernelVersion:  5.7
18Contact:        linux-accelerators@lists.ozlabs.org
19Description:    Available instances left of the device
20                Return -ENODEV if uacce_ops get_available_instances is not provided
21
22What:           /sys/class/uacce/<dev_name>/algorithms
23Date:           Feb 2020
24KernelVersion:  5.7
25Contact:        linux-accelerators@lists.ozlabs.org
26Description:    Algorithms supported by this accelerator, separated by new line.
27                Can be any string and up to userspace to parse.
28
29What:           /sys/class/uacce/<dev_name>/region_mmio_size
30Date:           Feb 2020
31KernelVersion:  5.7
32Contact:        linux-accelerators@lists.ozlabs.org
33Description:    Size (bytes) of mmio region queue file
34
35What:           /sys/class/uacce/<dev_name>/region_dus_size
36Date:           Feb 2020
37KernelVersion:  5.7
38Contact:        linux-accelerators@lists.ozlabs.org
39Description:    Size (bytes) of dus region queue file
40