brintos

brintos / linux-shallow public Read only

0
0
Text · 3.7 KiB · 6565826 Raw
102 lines · plain
1What:		/sys/bus/platform/devices/dfl-port.0/id2Date:		June 20183KernelVersion:	4.194Contact:	Wu Hao <hao.wu@intel.com>5Description:	Read-only. It returns id of this port. One DFL FPGA device6		may have more than one port. Userspace could use this id to7		distinguish different ports under same FPGA device.8 9What:		/sys/bus/platform/devices/dfl-port.0/afu_id10Date:		June 201811KernelVersion:	4.1912Contact:	Wu Hao <hao.wu@intel.com>13Description:	Read-only. User can program different PR bitstreams to FPGA14		Accelerator Function Unit (AFU) for different functions. It15		returns uuid which could be used to identify which PR bitstream16		is programmed in this AFU.17 18What:		/sys/bus/platform/devices/dfl-port.0/power_state19Date:		August 201920KernelVersion:	5.421Contact:	Wu Hao <hao.wu@intel.com>22Description:	Read-only. It reports the APx (AFU Power) state, different APx23		means different throttling level. When reading this file, it24		returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.25 26What:		/sys/bus/platform/devices/dfl-port.0/ap1_event27Date:		August 201928KernelVersion:	5.429Contact:	Wu Hao <hao.wu@intel.com>30Description:	Read-write. Read this file for AP1 (AFU Power State 1) event.31		It's used to indicate transient AP1 state. Write 1 to this32		file to clear AP1 event.33 34What:		/sys/bus/platform/devices/dfl-port.0/ap2_event35Date:		August 201936KernelVersion:	5.437Contact:	Wu Hao <hao.wu@intel.com>38Description:	Read-write. Read this file for AP2 (AFU Power State 2) event.39		It's used to indicate transient AP2 state. Write 1 to this40		file to clear AP2 event.41 42What:		/sys/bus/platform/devices/dfl-port.0/ltr43Date:		August 201944KernelVersion:	5.445Contact:	Wu Hao <hao.wu@intel.com>46Description:	Read-write. Read or set AFU latency tolerance reporting value.47		Set ltr to 1 if the AFU can tolerate latency >= 40us or set it48		to 0 if it is latency sensitive.49 50What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcmd51Date:		August 201952KernelVersion:	5.453Contact:	Wu Hao <hao.wu@intel.com>54Description:	Write-only. User writes command to this interface to set55		userclock to AFU.56 57What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqsts58Date:		August 201959KernelVersion:	5.460Contact:	Wu Hao <hao.wu@intel.com>61Description:	Read-only. Read this file to get the status of issued command62		to userclck_freqcmd.63 64What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcntrcmd65Date:		August 201966KernelVersion:	5.467Contact:	Wu Hao <hao.wu@intel.com>68Description:	Write-only. User writes command to this interface to set69		userclock counter.70 71What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcntrsts72Date:		August 201973KernelVersion:	5.474Contact:	Wu Hao <hao.wu@intel.com>75Description:	Read-only. Read this file to get the status of issued command76		to userclck_freqcntrcmd.77 78What:		/sys/bus/platform/devices/dfl-port.0/errors/errors79Date:		August 201980KernelVersion:	5.481Contact:	Wu Hao <hao.wu@intel.com>82Description:	Read-Write. Read this file to get errors detected on port and83		Accelerated Function Unit (AFU). Write error code to this file84		to clear errors. Write fails with -EINVAL if input parsing85		fails or input error code doesn't match. Write fails with86		-EBUSY or -ETIMEDOUT if error can't be cleared as hardware87		in low power state (-EBUSY) or not respoding (-ETIMEDOUT).88 89What:		/sys/bus/platform/devices/dfl-port.0/errors/first_error90Date:		August 201991KernelVersion:	5.492Contact:	Wu Hao <hao.wu@intel.com>93Description:	Read-only. Read this file to get the first error detected by94		hardware.95 96What:		/sys/bus/platform/devices/dfl-port.0/errors/first_malformed_req97Date:		August 201998KernelVersion:	5.499Contact:	Wu Hao <hao.wu@intel.com>100Description:	Read-only. Read this file to get the first malformed request101		captured by hardware.102