61 lines · plain
1What: /sys/class/fpga_manager/<fpga>/name2Date: August 20153KernelVersion: 4.34Contact: Alan Tull <atull@opensource.altera.com>5Description: Name of low level fpga manager driver.6 7What: /sys/class/fpga_manager/<fpga>/state8Date: August 20159KernelVersion: 4.310Contact: Alan Tull <atull@opensource.altera.com>11Description: Read fpga manager state as a string.12 The intent is to provide enough detail that if something goes13 wrong during FPGA programming (something that the driver can't14 fix) then userspace can know, i.e. if the firmware request15 fails, that could be due to not being able to find the firmware16 file.17 18 This is a superset of FPGA states and fpga manager driver19 states. The fpga manager driver is walking through these steps20 to get the FPGA into a known operating state. It's a sequence,21 though some steps may get skipped. Valid FPGA states will vary22 by manufacturer; this is a superset.23 24 * unknown = can't determine state25 * power off = FPGA power is off26 * power up = FPGA reports power is up27 * reset = FPGA held in reset state28 * firmware request = firmware class request in progress29 * firmware request error = firmware request failed30 * write init = preparing FPGA for programming31 * write init error = Error while preparing FPGA for programming32 * write = FPGA ready to receive image data33 * write error = Error while programming34 * write complete = Doing post programming steps35 * write complete error = Error while doing post programming36 * operating = FPGA is programmed and operating37 38What: /sys/class/fpga_manager/<fpga>/status39Date: June 201840KernelVersion: 4.1941Contact: Wu Hao <hao.wu@intel.com>42Description: Read fpga manager status as a string.43 If FPGA programming operation fails, it could be caused by crc44 error or incompatible bitstream image. The intent of this45 interface is to provide more detailed information for FPGA46 programming errors to userspace. This is a list of strings for47 the supported status.48 49 * reconfig operation error - invalid operations detected by50 reconfiguration hardware.51 e.g. start reconfiguration52 with errors not cleared53 * reconfig CRC error - CRC error detected by54 reconfiguration hardware.55 * reconfig incompatible image - reconfiguration image is56 incompatible with hardware57 * reconfig IP protocol error - protocol errors detected by58 reconfiguration hardware59 * reconfig fifo overflow error - FIFO overflow detected by60 reconfiguration hardware61