Lines Matching full:fpga
2 FPGA Device Feature List (DFL) Framework Overview
11 The Device Feature List (DFL) FPGA framework (and drivers according to
14 configure, enumerate, open and access FPGA accelerators on platforms which
16 enables system level management functions such as FPGA reconfiguration.
23 walk through these predefined data structures to enumerate FPGA features:
24 FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
55 FPGA Interface Unit (FIU) represents a standalone functional unit for the
56 interface to FPGA, e.g. the FPGA Management Engine (FME) and Port (more
59 Accelerated Function Unit (AFU) represents a FPGA programmable region and
74 and can be implemented in register regions of any FPGA device.
77 FIU - FME (FPGA Management Engine)
79 The FPGA Management Engine performs reconfiguration and other infrastructure
80 functions. Each FPGA device only has one FME.
99 bitstream_id indicates version of the static FPGA region.
102 bitstream_metadata includes detailed information of static FPGA region,
106 one FPGA device may have more than one port, this sysfs interface indicates
107 how many ports the FPGA device has.
131 A port represents the interface between the static FPGA fabric and a partially
133 to the accelerator and exposes features such as reset and debug. Each FPGA
160 reset the FPGA Port and its AFU. Userspace can do Port
188 | FPGA Container Device | Device Feature List
189 | (FPGA Base Region) | Framework
193 | FPGA DFL Device Module |
197 | FPGA Hardware Device |
201 (FPGA base region), discover feature devices and their private features from the
207 The FPGA DFL Device could be different hardwares, e.g. PCIe device, platform
212 (Please refer to drivers/fpga/dfl.c for detailed enumeration APIs).
214 The FPGA Management Engine (FME) driver is a platform driver which is loaded
216 provides the key features for FPGA management, including:
218 a) Expose static FPGA region information, e.g. version and metadata.
222 b) Partial Reconfiguration. The FME driver creates FPGA manager, FPGA
223 bridges and FPGA regions during PR sub feature initialization. Once
225 common interface function from FPGA Region to complete the partial
228 Similar to the FME driver, the FPGA Accelerated Function Unit (AFU) driver is
244 generated for the exact static FPGA region and targeted reconfigurable region
245 (port) of the FPGA, otherwise, the reconfiguration operation will fail and
248 the compat_id exposed by the target FPGA region. This check is usually done by
252 FPGA virtualization - PCIe SRIOV
254 This section describes the virtualization support on DFL based FPGA device to
256 (VM). This section only describes the PCIe based FPGA device with SRIOV support.
258 Features supported by the particular FPGA device are exposed through Device
279 | DFL based FPGA PCIe Device |
294 | FPGA || FPGA || FPGA | |
302 | FPGA Container Device | | | FPGA Container Device |
303 | (FPGA Base Region) | | | (FPGA Base Region) |
306 | FPGA PCIE Module | | Virtual | FPGA PCIE Module |
313 FPGA PCIe device driver is always loaded first once a FPGA PCIe PF or VF device
316 * Finishes enumeration on both FPGA PCIe PF and VF device using common
349 This section introduces how applications enumerate the fpga device from
352 In the example below, two DFL based FPGA devices are installed in the host. Each
353 fpga device has one FME and two ports (AFUs).
355 FPGA regions are created under /sys/class/fpga_region/::
364 fpga region which represents the FPGA device.
398 FPGA cache hit/miss rate, transaction number, interface clock counter of AFU
399 and other FPGA performance events.
401 Different FPGA devices may have different counter sets, depending on hardware
402 implementation. E.g., some discrete FPGA cards don't have any cache. User could
413 category; "portid" is introduced to decide counters set to monitor on FPGA
466 since they are system-wide counters on FPGA device.
501 FME Partial Reconfiguration Sub Feature driver (see drivers/fpga/dfl-fme-pr.c)