1 What: /sys/class/uacce/<dev_name>/api
4 Contact: linux-accelerators@lists.ozlabs.org
5 Description: 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
9 What: /sys/class/uacce/<dev_name>/flags
12 Contact: linux-accelerators@lists.ozlabs.org
13 Description: Attributes of the device, see UACCE_DEV_xxx flag defined in uacce.h
15 What: /sys/class/uacce/<dev_name>/available_instances
18 Contact: linux-accelerators@lists.ozlabs.org
19 Description: Available instances left of the device
20 Return -ENODEV if uacce_ops get_available_instances is not provided
22 What: /sys/class/uacce/<dev_name>/isolate_strategy
25 Contact: linux-accelerators@lists.ozlabs.org
26 Description: (RW) A sysfs node that configure the error threshold for the hardware
27 isolation strategy. This size is a configured integer value, which is the
28 number of threshold for hardware errors occurred in one hour. The default is 0.
29 0 means never isolate the device. The maximum value is 65535. You can write
30 a number of threshold based on your hardware.
32 What: /sys/class/uacce/<dev_name>/isolate
35 Contact: linux-accelerators@lists.ozlabs.org
36 Description: (R) A sysfs node that read the device isolated state. The value 1
37 means the device is unavailable. The 0 means the device is
40 What: /sys/class/uacce/<dev_name>/algorithms
43 Contact: linux-accelerators@lists.ozlabs.org
44 Description: Algorithms supported by this accelerator, separated by new line.
45 Can be any string and up to userspace to parse.
47 What: /sys/class/uacce/<dev_name>/region_mmio_size
50 Contact: linux-accelerators@lists.ozlabs.org
51 Description: Size (bytes) of mmio region queue file
53 What: /sys/class/uacce/<dev_name>/region_dus_size
56 Contact: linux-accelerators@lists.ozlabs.org
57 Description: Size (bytes) of dus region queue file