OPAE Intel FPGA Linux Device Driver Architecture Guide

Download PDF
ID 683857
Date 10/02/2017
Public

Visible to Intel only — GUID: bry1503626345713

Ixiasoft

View Details

Document Table of Contents
Document Table of Contents x
1. OPAE Intel® FPGA Linux Device Driver Architecture
1. OPAE Intel® FPGA Linux Device Driver Architecture x
1.1. Hardware Architecture 1.2. sysfs Files 1.3. Revision History
1.1. Hardware Architecture x
1.1.1. FPGA Management Engine (FME) 1.1.2. Port 1.1.3. Accelerator Function (AF) Unit 1.1.4. Partial Reconfiguration 1.1.5. FPGA Virtualization 1.1.6. Driver Organization 1.1.7. Application FPGA Device Enumeration 1.1.8. PCIe Driver Enumeration 1.1.9. FME Platform Device Initialization 1.1.10. Port Platform Device Initialization 1.1.11. FME IOCTLs 1.1.12. Port IOCTLs
1.1.6. Driver Organization x
1.1.6.1. PCIe Module Device Driver 1.1.6.2. PCIe Module Device Driver Functions 1.1.6.3. FME Platform Module Device Driver 1.1.6.4. FME Platform Module Device Driver Functions 1.1.6.5. Port Platform Module Device Driver 1.1.6.6. Port Platform Module Device Driver Functions
1.1.8. PCIe Driver Enumeration x
1.1.8.1. Enumeration Data Structures 1.1.8.2. Enumeration Flow
1.1.9. FME Platform Device Initialization x
1.1.9.1. FME Platform Device Data Structures 1.1.9.2. FME Platform Device Initialization Flow
1.1.10. Port Platform Device Initialization x
1.1.10.1. Port Platform Device Data Structures 1.1.10.2. Port Platform Device Initialization Flow
1.2. sysfs Files x
1.2.1. FME Header sysfs files 1.2.2. FME Thermal Management sysfs files 1.2.3. FME Power Management sysfs files 1.2.4. FME Global Error sysfs files 1.2.5. FME Partial Reconfiguration sysfs files 1.2.6. FME Global Performance sysfs files 1.2.7. Port Header sysfs files 1.2.8. Port AFU Header sysfs files 1.2.9. Port Error sysfs files
1. OPAE Intel® FPGA Linux Device Driver Architecture

1.1.7. Application FPGA Device Enumeration

This section introduces how applications enumerate the FPGA device from the sysfs hierarchy under /sys/class/fpga.

In the example below, two Intel® FPGA devices are installed in the host. Each FPGA device has one FME and two Ports (AFUs).

For each FPGA device, a device directory is created under /sys/class/fpga: 
/sys/class/fpga/intel-fpga-dev.0 
/sys/class/fpga/intel-fpga-dev.1
Each node has one FME and two Ports (AFUs) as child devices: 
/sys/class/fpga/intel-fpga-dev.0/intel-fpga-fme.0 
/sys/class/fpga/intel-fpga-dev.0/intel-fpga-port.0 
/sys/class/fpga/intel-fpga-dev.0/intel-fpga-port.1 

/sys/class/fpga/intel-fpga-dev.1/intel-fpga-fme.1 
/sys/class/fpga/intel-fpga-dev.1/intel-fpga-port.2 
/sys/class/fpga/intel-fpga-dev.1/intel-fpga-port.3
In general, the FME/Port sysfs interfaces are named as follows: 
/sys/class/fpga/intel-fpga-dev.i/intel-fpga-fme.j/ 
/sys/class/fpga/intel-fpga-dev.i/intel-fpga-port.k/

with i consecutively numbering all the container devices, j consecutively numbering the FME’s and k consecutively numbering all Ports.

The device nodes used for ioctl() and mmap() can be referenced through: 
/dev/intel-fpga-fme.j 
/dev/intel-fpga-port.k
Level Two Title