€•(     Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ/translations/zh_CN/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/zh_TW/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/it_IT/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ja_JP/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ko_KR/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/sp_SP/fpga/dfl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ1FPGA Device Feature List (DFL) Framework Overview”h]”hŒ1FPGA Device Feature List (DFL) Framework Overview”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ6/var/lib/git/docbuild/linux/Documentation/fpga/dfl.rst”h KubhŒ	paragraph”“”)”}”(hŒAuthors:”h]”hŒAuthors:”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ'Enno Luebbers <enno.luebbers@intel.com>”h]”h¸)”}”(hhÐh]”(hŒEnno Luebbers <”…””}”(hhÒhžhhŸNh NubhŒ	reference”“”)”}”(hŒenno.luebbers@intel.com”h]”hŒenno.luebbers@intel.com”…””}”(hhÛhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:enno.luebbers@intel.com”uh1hÙhhÒubhŒ>”…””}”(hhÒhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÎubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hŒ/Xiao Guangrong <guangrong.xiao@linux.intel.com>”h]”h¸)”}”(hhýh]”(hŒXiao Guangrong <”…””}”(hhÿhžhhŸNh NubhÚ)”}”(hŒguangrong.xiao@linux.intel.com”h]”hŒguangrong.xiao@linux.intel.com”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ%mailto:guangrong.xiao@linux.intel.com”uh1hÙhhÿubhŒ>”…””}”(hhÿhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhûubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hŒWu Hao <hao.wu@intel.com>”h]”h¸)”}”(hj(  h]”(hŒWu Hao <”…””}”(hj*  hžhhŸNh NubhÚ)”}”(hŒhao.wu@intel.com”h]”hŒhao.wu@intel.com”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:hao.wu@intel.com”uh1hÙhj*  ubhŒ>”…””}”(hj*  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K	hj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hŒXu Yilun <yilun.xu@intel.com>
”h]”h¸)”}”(hŒXu Yilun <yilun.xu@intel.com>”h]”(hŒ
Xu Yilun <”…””}”(hjU  hžhhŸNh NubhÚ)”}”(hŒyilun.xu@intel.com”h]”hŒyilun.xu@intel.com”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:yilun.xu@intel.com”uh1hÙhjU  ubhŒ>”…””}”(hjU  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K
hjQ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hÇhŸh¶h Khh£hžhubh¸)”}”(hX·  The Device Feature List (DFL) FPGA framework (and drivers according to
this framework) hides the very details of low layer hardware and provides
unified interfaces to userspace. Applications could use these interfaces to
configure, enumerate, open and access FPGA accelerators on platforms which
implement the DFL in the device memory. Besides this, the DFL framework
enables system level management functions such as FPGA reconfiguration.”h]”hX·  The Device Feature List (DFL) FPGA framework (and drivers according to
this framework) hides the very details of low layer hardware and provides
unified interfaces to userspace. Applications could use these interfaces to
configure, enumerate, open and access FPGA accelerators on platforms which
implement the DFL in the device memory. Besides this, the DFL framework
enables system level management functions such as FPGA reconfiguration.”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒ"Device Feature List (DFL) Overview”h]”hŒ"Device Feature List (DFL) Overview”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj“  hžhhŸh¶h Kubh¸)”}”(hXO  Device Feature List (DFL) defines a linked list of feature headers within the
device MMIO space to provide an extensible way of adding features. Software can
walk through these predefined data structures to enumerate FPGA features:
FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
as illustrated below::”h]”hXN  Device Feature List (DFL) defines a linked list of feature headers within the
device MMIO space to provide an extensible way of adding features. Software can
walk through these predefined data structures to enumerate FPGA features:
FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
as illustrated below:”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj“  hžhubhŒliteral_block”“”)”}”(hXF     Header            Header            Header            Header
+----------+  +-->+----------+  +-->+----------+  +-->+----------+
|   Type   |  |   |  Type    |  |   |  Type    |  |   |  Type    |
|   FIU    |  |   | Private  |  |   | Private  |  |   | Private  |
+----------+  |   | Feature  |  |   | Feature  |  |   | Feature  |
| Next_DFH |--+   +----------+  |   +----------+  |   +----------+
+----------+      | Next_DFH |--+   | Next_DFH |--+   | Next_DFH |--> NULL
|    ID    |      +----------+      +----------+      +----------+
+----------+      |    ID    |      |    ID    |      |    ID    |
| Next_AFU |--+   +----------+      +----------+      +----------+
+----------+  |   | Feature  |      | Feature  |      | Feature  |
|  Header  |  |   | Register |      | Register |      | Register |
| Register |  |   |   Set    |      |   Set    |      |   Set    |
|   Set    |  |   +----------+      +----------+      +----------+
+----------+  |      Header
              +-->+----------+
                  |   Type   |
                  |   AFU    |
                  +----------+
                  | Next_DFH |--> NULL
                  +----------+
                  |   GUID   |
                  +----------+
                  |  Header  |
                  | Register |
                  |   Set    |
                  +----------+”h]”hXF     Header            Header            Header            Header
+----------+  +-->+----------+  +-->+----------+  +-->+----------+
|   Type   |  |   |  Type    |  |   |  Type    |  |   |  Type    |
|   FIU    |  |   | Private  |  |   | Private  |  |   | Private  |
+----------+  |   | Feature  |  |   | Feature  |  |   | Feature  |
| Next_DFH |--+   +----------+  |   +----------+  |   +----------+
+----------+      | Next_DFH |--+   | Next_DFH |--+   | Next_DFH |--> NULL
|    ID    |      +----------+      +----------+      +----------+
+----------+      |    ID    |      |    ID    |      |    ID    |
| Next_AFU |--+   +----------+      +----------+      +----------+
+----------+  |   | Feature  |      | Feature  |      | Feature  |
|  Header  |  |   | Register |      | Register |      | Register |
| Register |  |   |   Set    |      |   Set    |      |   Set    |
|   Set    |  |   +----------+      +----------+      +----------+
+----------+  |      Header
              +-->+----------+
                  |   Type   |
                  |   AFU    |
                  +----------+
                  | Next_DFH |--> NULL
                  +----------+
                  |   GUID   |
                  +----------+
                  |  Header  |
                  | Register |
                  |   Set    |
                  +----------+”…””}”hj´  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j²  hŸh¶h Khj“  hžhubh¸)”}”(hŒÂFPGA Interface Unit (FIU) represents a standalone functional unit for the
interface to FPGA, e.g. the FPGA Management Engine (FME) and Port (more
descriptions on FME and Port in later sections).”h]”hŒÂFPGA Interface Unit (FIU) represents a standalone functional unit for the
interface to FPGA, e.g. the FPGA Management Engine (FME) and Port (more
descriptions on FME and Port in later sections).”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K8hj“  hžhubh¸)”}”(hŒ”Accelerated Function Unit (AFU) represents an FPGA programmable region and
always connects to a FIU (e.g. a Port) as its child as illustrated above.”h]”hŒ”Accelerated Function Unit (AFU) represents an FPGA programmable region and
always connects to a FIU (e.g. a Port) as its child as illustrated above.”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K<hj“  hžhubh¸)”}”(hX  Private Features represent sub features of the FIU and AFU. They could be
various function blocks with different IDs, but all private features which
belong to the same FIU or AFU, must be linked to one list via the Next Device
Feature Header (Next_DFH) pointer.”h]”hX  Private Features represent sub features of the FIU and AFU. They could be
various function blocks with different IDs, but all private features which
belong to the same FIU or AFU, must be linked to one list via the Next Device
Feature Header (Next_DFH) pointer.”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K?hj“  hžhubh¸)”}”(hX5  Each FIU, AFU and Private Feature could implement its own functional registers.
The functional register set for FIU and AFU, is named as Header Register Set,
e.g. FME Header Register Set, and the one for Private Feature, is named as
Feature Register Set, e.g. FME Partial Reconfiguration Feature Register Set.”h]”hX5  Each FIU, AFU and Private Feature could implement its own functional registers.
The functional register set for FIU and AFU, is named as Header Register Set,
e.g. FME Header Register Set, and the one for Private Feature, is named as
Feature Register Set, e.g. FME Partial Reconfiguration Feature Register Set.”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KDhj“  hžhubh¸)”}”(hŒÖThis Device Feature List provides a way of linking features together, it's
convenient for software to locate each feature by walking through this list,
and can be implemented in register regions of any FPGA device.”h]”hŒØThis Device Feature List provides a way of linking features together, itâ€™s
convenient for software to locate each feature by walking through this list,
and can be implemented in register regions of any FPGA device.”…””}”(hjü  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KIhj“  hžhubeh}”(h]”Œ device-feature-list-dfl-overview”ah ]”h"]”Œ"device feature list (dfl) overview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ!Device Feature Header - Version 0”h]”hŒ!Device Feature Header - Version 0”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h KOubh¸)”}”(hŒ¢Version 0 (DFHv0) is the original version of the Device Feature Header.
All multi-byte quantities in DFHv0 are little-endian.
The format of DFHv0 is shown below::”h]”hŒ¡Version 0 (DFHv0) is the original version of the Device Feature Header.
All multi-byte quantities in DFHv0 are little-endian.
The format of DFHv0 is shown below:”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KPhj  hžhubj³  )”}”(hX  +-----------------------------------------------------------------------+
|63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 REV 12|11 ID 0| 0x00
+-----------------------------------------------------------------------+
|63                                 GUID_L                             0| 0x08
+-----------------------------------------------------------------------+
|63                                 GUID_H                             0| 0x10
+-----------------------------------------------------------------------+”h]”hX  +-----------------------------------------------------------------------+
|63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 REV 12|11 ID 0| 0x00
+-----------------------------------------------------------------------+
|63                                 GUID_L                             0| 0x08
+-----------------------------------------------------------------------+
|63                                 GUID_H                             0| 0x10
+-----------------------------------------------------------------------+”…””}”hj1  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h KThj  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hX  Offset 0x00

* Type - The type of DFH (e.g. FME, AFU, or private feature).
* DFH VER - The version of the DFH.
* Rsvd - Currently unused.
* EOL - Set if the DFH is the end of the Device Feature List (DFL).
* Next - The offset in bytes of the next DFH in the DFL from the DFH start,
  and the start of a DFH must be aligned to an 8 byte boundary.
  If EOL is set, Next is the size of MMIO of the last feature in the list.
* REV - The revision of the feature associated with this header.
* ID - The feature ID if Type is private feature.
”h]”(h¸)”}”(hŒOffset 0x00”h]”hŒOffset 0x00”…””}”(hjF  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K\hjB  ubhÈ)”}”(hhh]”(hÍ)”}”(hŒ;Type - The type of DFH (e.g. FME, AFU, or private feature).”h]”h¸)”}”(hjY  h]”hŒ;Type - The type of DFH (e.g. FME, AFU, or private feature).”…””}”(hj[  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K^hjW  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒ!DFH VER - The version of the DFH.”h]”h¸)”}”(hjp  h]”hŒ!DFH VER - The version of the DFH.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K_hjn  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒRsvd - Currently unused.”h]”h¸)”}”(hj‡  h]”hŒRsvd - Currently unused.”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K`hj…  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒAEOL - Set if the DFH is the end of the Device Feature List (DFL).”h]”h¸)”}”(hjž  h]”hŒAEOL - Set if the DFH is the end of the Device Feature List (DFL).”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kahjœ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”h]”h¸)”}”(hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”h]”hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kbhj³  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒ>REV - The revision of the feature associated with this header.”h]”h¸)”}”(hjÍ  h]”hŒ>REV - The revision of the feature associated with this header.”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KehjË  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubhÍ)”}”(hŒ0ID - The feature ID if Type is private feature.
”h]”h¸)”}”(hŒ/ID - The feature ID if Type is private feature.”h]”hŒ/ID - The feature ID if Type is private feature.”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kfhjâ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjT  ubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  Œ*”uh1hÇhŸh¶h K^hjB  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj?  hžhhŸNh NubhÍ)”}”(hŒ‚Offset 0x08

* GUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier
  (present only if Type is FME or AFU).
”h]”(h¸)”}”(hŒOffset 0x08”h]”hŒOffset 0x08”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhj  ubhÈ)”}”(hhh]”hÍ)”}”(hŒqGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).
”h]”h¸)”}”(hŒpGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).”h]”hŒpGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kjhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h Kjhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj?  hžhhŸNh NubhÍ)”}”(hŒ‚Offset 0x10

* GUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier
  (present only if Type is FME or AFU).

”h]”(h¸)”}”(hŒOffset 0x10”h]”hŒOffset 0x10”…””}”(hjD  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kmhj@  ubhÈ)”}”(hhh]”hÍ)”}”(hŒqGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).

”h]”h¸)”}”(hŒoGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).”h]”hŒoGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier
(present only if Type is FME or AFU).”…””}”(hjY  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KohjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjR  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h Kohj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj?  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j„  uh1hÇhŸh¶h K\hj  hžhubeh}”(h]”Œdevice-feature-header-version-0”ah ]”h"]”Œ!device feature header - version 0”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KOubh¢)”}”(hhh]”(h§)”}”(hŒ!Device Feature Header - Version 1”h]”hŒ!Device Feature Header - Version 1”…””}”(hjŠ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj‡  hžhhŸh¶h Ktubh¸)”}”(hŒPVersion 1 (DFHv1) of the Device Feature Header adds the following functionality:”h]”hŒPVersion 1 (DFHv1) of the Device Feature Header adds the following functionality:”…””}”(hj˜  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kuhj‡  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hŒ_Provides a standardized mechanism for features to describe
parameters/capabilities to software.”h]”h¸)”}”(hŒ_Provides a standardized mechanism for features to describe
parameters/capabilities to software.”h]”hŒ_Provides a standardized mechanism for features to describe
parameters/capabilities to software.”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kwhj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj¦  hžhhŸh¶h NubhÍ)”}”(hŒ2Standardize the use of a GUID for all DFHv1 types.”h]”h¸)”}”(hjÃ  h]”hŒ2Standardize the use of a GUID for all DFHv1 types.”…””}”(hjÅ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KyhjÁ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj¦  hžhhŸh¶h NubhÍ)”}”(hŒJDecouples the DFH location from the register space of the feature itself.
”h]”h¸)”}”(hŒIDecouples the DFH location from the register space of the feature itself.”h]”hŒIDecouples the DFH location from the register space of the feature itself.”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KzhjØ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj¦  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h Kwhj‡  hžhubh¸)”}”(hŒAll multi-byte quantities in DFHv1 are little-endian.
The format of Version 1 of the Device Feature Header (DFH) is shown below::”h]”hŒ€All multi-byte quantities in DFHv1 are little-endian.
The format of Version 1 of the Device Feature Header (DFH) is shown below:”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K|hj‡  hžhubj³  )”}”(hX  +-----------------------------------------------------------------------+
|63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 REV 12|11 ID 0| 0x00
+-----------------------------------------------------------------------+
|63                                 GUID_L                             0| 0x08
+-----------------------------------------------------------------------+
|63                                 GUID_H                             0| 0x10
+-----------------------------------------------------------------------+
|63                   Reg Address/Offset                      1|  Rel  0| 0x18
+-----------------------------------------------------------------------+
|63        Reg Size       32|Params 31|30 Group    16|15 Instance      0| 0x20
+-----------------------------------------------------------------------+
|63 Next    35|34RSV33|EOP32|31 Param Version 16|15 Param ID           0| 0x28
+-----------------------------------------------------------------------+
|63                 Parameter Data                                     0| 0x30
+-----------------------------------------------------------------------+

                              ...

+-----------------------------------------------------------------------+
|63 Next    35|34RSV33|EOP32|31 Param Version 16|15 Param ID           0|
+-----------------------------------------------------------------------+
|63                 Parameter Data                                     0|
+-----------------------------------------------------------------------+”h]”hX  +-----------------------------------------------------------------------+
|63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 REV 12|11 ID 0| 0x00
+-----------------------------------------------------------------------+
|63                                 GUID_L                             0| 0x08
+-----------------------------------------------------------------------+
|63                                 GUID_H                             0| 0x10
+-----------------------------------------------------------------------+
|63                   Reg Address/Offset                      1|  Rel  0| 0x18
+-----------------------------------------------------------------------+
|63        Reg Size       32|Params 31|30 Group    16|15 Instance      0| 0x20
+-----------------------------------------------------------------------+
|63 Next    35|34RSV33|EOP32|31 Param Version 16|15 Param ID           0| 0x28
+-----------------------------------------------------------------------+
|63                 Parameter Data                                     0| 0x30
+-----------------------------------------------------------------------+

                              ...

+-----------------------------------------------------------------------+
|63 Next    35|34RSV33|EOP32|31 Param Version 16|15 Param ID           0|
+-----------------------------------------------------------------------+
|63                 Parameter Data                                     0|
+-----------------------------------------------------------------------+”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h Khj‡  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hX  Offset 0x00

* Type - The type of DFH (e.g. FME, AFU, or private feature).
* DFH VER - The version of the DFH.
* Rsvd - Currently unused.
* EOL - Set if the DFH is the end of the Device Feature List (DFL).
* Next - The offset in bytes of the next DFH in the DFL from the DFH start,
  and the start of a DFH must be aligned to an 8 byte boundary.
  If EOL is set, Next is the size of MMIO of the last feature in the list.
* REV - The revision of the feature associated with this header.
* ID - The feature ID if Type is private feature.
”h]”(h¸)”}”(hŒOffset 0x00”h]”hŒOffset 0x00”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K—hj  ubhÈ)”}”(hhh]”(hÍ)”}”(hŒ;Type - The type of DFH (e.g. FME, AFU, or private feature).”h]”h¸)”}”(hj,  h]”hŒ;Type - The type of DFH (e.g. FME, AFU, or private feature).”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K™hj*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒ!DFH VER - The version of the DFH.”h]”h¸)”}”(hjC  h]”hŒ!DFH VER - The version of the DFH.”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KšhjA  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒRsvd - Currently unused.”h]”h¸)”}”(hjZ  h]”hŒRsvd - Currently unused.”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K›hjX  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒAEOL - Set if the DFH is the end of the Device Feature List (DFL).”h]”h¸)”}”(hjq  h]”hŒAEOL - Set if the DFH is the end of the Device Feature List (DFL).”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kœhjo  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”h]”h¸)”}”(hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”h]”hŒÐNext - The offset in bytes of the next DFH in the DFL from the DFH start,
and the start of a DFH must be aligned to an 8 byte boundary.
If EOL is set, Next is the size of MMIO of the last feature in the list.”…””}”(hjŠ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj†  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒ>REV - The revision of the feature associated with this header.”h]”h¸)”}”(hj   h]”hŒ>REV - The revision of the feature associated with this header.”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hjž  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubhÍ)”}”(hŒ0ID - The feature ID if Type is private feature.
”h]”h¸)”}”(hŒ/ID - The feature ID if Type is private feature.”h]”hŒ/ID - The feature ID if Type is private feature.”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¡hjµ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj'  ubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h K™hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒ[Offset 0x08

* GUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier.
”h]”(h¸)”}”(hŒOffset 0x08”h]”hŒOffset 0x08”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K£hjÙ  ubhÈ)”}”(hhh]”hÍ)”}”(hŒLGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier.
”h]”h¸)”}”(hŒKGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier.”h]”hŒKGUID_L - Least significant 64 bits of a 128-bit Globally Unique Identifier.”…””}”(hjò  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¥hjî  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjë  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h K¥hjÙ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒZOffset 0x10

* GUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier.
”h]”(h¸)”}”(hŒOffset 0x10”h]”hŒOffset 0x10”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K§hj  ubhÈ)”}”(hhh]”hÍ)”}”(hŒKGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier.
”h]”h¸)”}”(hŒJGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier.”h]”hŒJGUID_H - Most significant 64 bits of a 128-bit Globally Unique Identifier.”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K©hj'  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj$  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h K©hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒ÷Offset 0x18

* Reg Address/Offset - If Rel bit is set, then the value is the high 63 bits
  of a 16-bit aligned absolute address of the feature's registers. Otherwise
  the value is the offset from the start of the DFH of the feature's registers.
”h]”(h¸)”}”(hŒOffset 0x18”h]”hŒOffset 0x18”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K«hjK  ubhÈ)”}”(hhh]”hÍ)”}”(hŒäReg Address/Offset - If Rel bit is set, then the value is the high 63 bits
of a 16-bit aligned absolute address of the feature's registers. Otherwise
the value is the offset from the start of the DFH of the feature's registers.
”h]”h¸)”}”(hŒãReg Address/Offset - If Rel bit is set, then the value is the high 63 bits
of a 16-bit aligned absolute address of the feature's registers. Otherwise
the value is the offset from the start of the DFH of the feature's registers.”h]”hŒçReg Address/Offset - If Rel bit is set, then the value is the high 63 bits
of a 16-bit aligned absolute address of the featureâ€™s registers. Otherwise
the value is the offset from the start of the DFH of the featureâ€™s registers.”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K­hj`  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj]  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h K­hjK  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒâOffset 0x20

* Reg Size - Size of feature's register set in bytes.
* Params - Set if DFH has a list of parameter blocks.
* Group - Id of group if feature is part of a group.
* Instance - Id of feature instance within a group.
”h]”(h¸)”}”(hŒOffset 0x20”h]”hŒOffset 0x20”…””}”(hjˆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K±hj„  ubhÈ)”}”(hhh]”(hÍ)”}”(hŒ3Reg Size - Size of feature's register set in bytes.”h]”h¸)”}”(hj›  h]”hŒ5Reg Size - Size of featureâ€™s register set in bytes.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K³hj™  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj–  ubhÍ)”}”(hŒ3Params - Set if DFH has a list of parameter blocks.”h]”h¸)”}”(hj²  h]”hŒ3Params - Set if DFH has a list of parameter blocks.”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K´hj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj–  ubhÍ)”}”(hŒ2Group - Id of group if feature is part of a group.”h]”h¸)”}”(hjÉ  h]”hŒ2Group - Id of group if feature is part of a group.”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KµhjÇ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj–  ubhÍ)”}”(hŒ2Instance - Id of feature instance within a group.
”h]”h¸)”}”(hŒ1Instance - Id of feature instance within a group.”h]”hŒ1Instance - Id of feature instance within a group.”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¶hjÞ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj–  ubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h K³hj„  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒßOffset 0x28 if feature has parameters

* Next - Offset to the next parameter block in 8 byte words. If EOP set,
  size in 8 byte words of last parameter.
* Param Version - Version of Param ID.
* Param ID - ID of parameter.
”h]”(h¸)”}”(hŒ%Offset 0x28 if feature has parameters”h]”hŒ%Offset 0x28 if feature has parameters”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¸hj  ubhÈ)”}”(hhh]”(hÍ)”}”(hŒnNext - Offset to the next parameter block in 8 byte words. If EOP set,
size in 8 byte words of last parameter.”h]”h¸)”}”(hŒnNext - Offset to the next parameter block in 8 byte words. If EOP set,
size in 8 byte words of last parameter.”h]”hŒnNext - Offset to the next parameter block in 8 byte words. If EOP set,
size in 8 byte words of last parameter.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kºhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒ$Param Version - Version of Param ID.”h]”h¸)”}”(hj1  h]”hŒ$Param Version - Version of Param ID.”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¼hj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒParam ID - ID of parameter.
”h]”h¸)”}”(hŒParam ID - ID of parameter.”h]”hŒParam ID - ID of parameter.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K½hjF  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h Kºhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh NubhÍ)”}”(hŒwOffset 0x30

* Parameter Data - Parameter data whose size and format is defined by
  version and ID of the parameter.

”h]”(h¸)”}”(hŒOffset 0x30”h]”hŒOffset 0x30”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¿hjj  ubhÈ)”}”(hhh]”hÍ)”}”(hŒfParameter Data - Parameter data whose size and format is defined by
version and ID of the parameter.

”h]”h¸)”}”(hŒdParameter Data - Parameter data whose size and format is defined by
version and ID of the parameter.”h]”hŒdParameter Data - Parameter data whose size and format is defined by
version and ID of the parameter.”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÁhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj|  ubah}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h KÁhjj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j„  uh1hÇhŸh¶h K—hj‡  hžhubeh}”(h]”Œdevice-feature-header-version-1”ah ]”h"]”Œ!device feature header - version 1”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Ktubh¢)”}”(hhh]”(h§)”}”(hŒ"FIU - FME (FPGA Management Engine)”h]”hŒ"FIU - FME (FPGA Management Engine)”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj±  hžhhŸh¶h KÆubh¸)”}”(hŒzThe FPGA Management Engine performs reconfiguration and other infrastructure
functions. Each FPGA device only has one FME.”h]”hŒzThe FPGA Management Engine performs reconfiguration and other infrastructure
functions. Each FPGA device only has one FME.”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÇhj±  hžhubh¸)”}”(hŒkUser-space applications can acquire exclusive access to the FME using open(),
and release it using close().”h]”hŒkUser-space applications can acquire exclusive access to the FME using open(),
and release it using close().”…””}”(hjÐ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÊhj±  hžhubh¸)”}”(hŒ3The following functions are exposed through ioctls:”h]”hŒ3The following functions are exposed through ioctls:”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÍhj±  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hŒ1Get driver API version (DFL_FPGA_GET_API_VERSION)”h]”h¸)”}”(hjñ  h]”hŒ1Get driver API version (DFL_FPGA_GET_API_VERSION)”…””}”(hjó  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÏhjï  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒ/Check for extensions (DFL_FPGA_CHECK_EXTENSION)”h]”h¸)”}”(hj  h]”hŒ/Check for extensions (DFL_FPGA_CHECK_EXTENSION)”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÐhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒ(Program bitstream (DFL_FPGA_FME_PORT_PR)”h]”h¸)”}”(hj  h]”hŒ(Program bitstream (DFL_FPGA_FME_PORT_PR)”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÑhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒ,Assign port to PF (DFL_FPGA_FME_PORT_ASSIGN)”h]”h¸)”}”(hj6  h]”hŒ,Assign port to PF (DFL_FPGA_FME_PORT_ASSIGN)”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÒhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒ0Release port from PF (DFL_FPGA_FME_PORT_RELEASE)”h]”h¸)”}”(hjM  h]”hŒ0Release port from PF (DFL_FPGA_FME_PORT_RELEASE)”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÓhjK  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒEGet number of irqs of FME global error (DFL_FPGA_FME_ERR_GET_IRQ_NUM)”h]”h¸)”}”(hjd  h]”hŒEGet number of irqs of FME global error (DFL_FPGA_FME_ERR_GET_IRQ_NUM)”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÔhjb  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h NubhÍ)”}”(hŒ?Set interrupt trigger for FME error (DFL_FPGA_FME_ERR_SET_IRQ)
”h]”h¸)”}”(hŒ>Set interrupt trigger for FME error (DFL_FPGA_FME_ERR_SET_IRQ)”h]”hŒ>Set interrupt trigger for FME error (DFL_FPGA_FME_ERR_SET_IRQ)”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÕhjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjì  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j„  uh1hÇhŸh¶h KÏhj±  hžhubh¸)”}”(hŒUMore functions are exposed through sysfs
(/sys/class/fpga_region/regionX/dfl-fme.n/):”h]”hŒUMore functions are exposed through sysfs
(/sys/class/fpga_region/regionX/dfl-fme.n/):”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K×hj±  hžhubhŒblock_quote”“”)”}”(hX  Read bitstream ID (bitstream_id)
    bitstream_id indicates version of the static FPGA region.

Read bitstream metadata (bitstream_metadata)
    bitstream_metadata includes detailed information of static FPGA region,
    e.g. synthesis date and seed.

Read number of ports (ports_num)
    one FPGA device may have more than one port, this sysfs interface indicates
    how many ports the FPGA device has.

Global error reporting management (errors/)
    error reporting sysfs interfaces allow user to read errors detected by the
    hardware, and clear the logged errors.

Power management (dfl_fme_power hwmon)
    power management hwmon sysfs interfaces allow user to read power management
    information (power consumption, thresholds, threshold status, limits, etc.)
    and configure power thresholds for different throttling levels.

Thermal management (dfl_fme_thermal hwmon)
    thermal management hwmon sysfs interfaces allow user to read thermal
    management information (current temperature, thresholds, threshold status,
    etc.).

Performance reporting
    performance counters are exposed through perf PMU APIs. Standard perf tool
    can be used to monitor all available perf events. Please see performance
    counter section below for more detailed information.

”h]”hŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒ[Read bitstream ID (bitstream_id)
bitstream_id indicates version of the static FPGA region.
”h]”(hŒterm”“”)”}”(hŒ Read bitstream ID (bitstream_id)”h]”hŒ Read bitstream ID (bitstream_id)”…””}”(hj¸  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h KÛhj²  ubhŒ
definition”“”)”}”(hhh]”h¸)”}”(hŒ9bitstream_id indicates version of the static FPGA region.”h]”hŒ9bitstream_id indicates version of the static FPGA region.”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÛhjÈ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj²  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h KÛhj­  ubj±  )”}”(hŒ“Read bitstream metadata (bitstream_metadata)
bitstream_metadata includes detailed information of static FPGA region,
e.g. synthesis date and seed.
”h]”(j·  )”}”(hŒ,Read bitstream metadata (bitstream_metadata)”h]”hŒ,Read bitstream metadata (bitstream_metadata)”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h Kßhjå  ubjÇ  )”}”(hhh]”h¸)”}”(hŒebitstream_metadata includes detailed information of static FPGA region,
e.g. synthesis date and seed.”h]”hŒebitstream_metadata includes detailed information of static FPGA region,
e.g. synthesis date and seed.”…””}”(hjú  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÞhj÷  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hjå  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Kßhj­  ubj±  )”}”(hŒ‘Read number of ports (ports_num)
one FPGA device may have more than one port, this sysfs interface indicates
how many ports the FPGA device has.
”h]”(j·  )”}”(hŒ Read number of ports (ports_num)”h]”hŒ Read number of ports (ports_num)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h Kãhj  ubjÇ  )”}”(hhh]”h¸)”}”(hŒoone FPGA device may have more than one port, this sysfs interface indicates
how many ports the FPGA device has.”h]”hŒoone FPGA device may have more than one port, this sysfs interface indicates
how many ports the FPGA device has.”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kâhj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Kãhj­  ubj±  )”}”(hŒžGlobal error reporting management (errors/)
error reporting sysfs interfaces allow user to read errors detected by the
hardware, and clear the logged errors.
”h]”(j·  )”}”(hŒ+Global error reporting management (errors/)”h]”hŒ+Global error reporting management (errors/)”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h KçhjC  ubjÇ  )”}”(hhh]”h¸)”}”(hŒqerror reporting sysfs interfaces allow user to read errors detected by the
hardware, and clear the logged errors.”h]”hŒqerror reporting sysfs interfaces allow user to read errors detected by the
hardware, and clear the logged errors.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KæhjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hjC  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Kçhj­  ubj±  )”}”(hŒÿPower management (dfl_fme_power hwmon)
power management hwmon sysfs interfaces allow user to read power management
information (power consumption, thresholds, threshold status, limits, etc.)
and configure power thresholds for different throttling levels.
”h]”(j·  )”}”(hŒ&Power management (dfl_fme_power hwmon)”h]”hŒ&Power management (dfl_fme_power hwmon)”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h Kìhjr  ubjÇ  )”}”(hhh]”h¸)”}”(hŒ×power management hwmon sysfs interfaces allow user to read power management
information (power consumption, thresholds, threshold status, limits, etc.)
and configure power thresholds for different throttling levels.”h]”hŒ×power management hwmon sysfs interfaces allow user to read power management
information (power consumption, thresholds, threshold status, limits, etc.)
and configure power thresholds for different throttling levels.”…””}”(hj‡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kêhj„  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hjr  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Kìhj­  ubj±  )”}”(hŒÂThermal management (dfl_fme_thermal hwmon)
thermal management hwmon sysfs interfaces allow user to read thermal
management information (current temperature, thresholds, threshold status,
etc.).
”h]”(j·  )”}”(hŒ*Thermal management (dfl_fme_thermal hwmon)”h]”hŒ*Thermal management (dfl_fme_thermal hwmon)”…””}”(hj¥  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h Kñhj¡  ubjÇ  )”}”(hhh]”h¸)”}”(hŒ–thermal management hwmon sysfs interfaces allow user to read thermal
management information (current temperature, thresholds, threshold status,
etc.).”h]”hŒ–thermal management hwmon sysfs interfaces allow user to read thermal
management information (current temperature, thresholds, threshold status,
etc.).”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kïhj³  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj¡  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Kñhj­  ubj±  )”}”(hŒàPerformance reporting
performance counters are exposed through perf PMU APIs. Standard perf tool
can be used to monitor all available perf events. Please see performance
counter section below for more detailed information.

”h]”(j·  )”}”(hŒPerformance reporting”h]”hŒPerformance reporting”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h K÷hjÐ  ubjÇ  )”}”(hhh]”h¸)”}”(hŒÈperformance counters are exposed through perf PMU APIs. Standard perf tool
can be used to monitor all available perf events. Please see performance
counter section below for more detailed information.”h]”hŒÈperformance counters are exposed through perf PMU APIs. Standard perf tool
can be used to monitor all available perf events. Please see performance
counter section below for more detailed information.”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kôhjâ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hjÐ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h K÷hj­  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j«  hj§  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¥  hŸh¶h KÚhj±  hžhubeh}”(h]”Œfiu-fme-fpga-management-engine”ah ]”h"]”Œ"fiu - fme (fpga management engine)”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÆubh¢)”}”(hhh]”(h§)”}”(hŒ
FIU - PORT”h]”hŒ
FIU - PORT”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj	  hžhhŸh¶h Kúubh¸)”}”(hX)  A port represents the interface between the static FPGA fabric and a partially
reconfigurable region containing an AFU. It controls the communication from SW
to the accelerator and exposes features such as reset and debug. Each FPGA
device may have more than one port, but always one AFU per port.”h]”hX)  A port represents the interface between the static FPGA fabric and a partially
reconfigurable region containing an AFU. It controls the communication from SW
to the accelerator and exposes features such as reset and debug. Each FPGA
device may have more than one port, but always one AFU per port.”…””}”(hj$	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kûhj	  hžhubeh}”(h]”Œfiu-port”ah ]”h"]”Œ
fiu - port”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kúubh¢)”}”(hhh]”(h§)”}”(hŒAFU”h]”hŒAFU”…””}”(hj=	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj:	  hžhhŸh¶h Mubh¸)”}”(hŒ~An AFU is attached to a port FIU and exposes a fixed length MMIO region to be
used for accelerator-specific control registers.”h]”hŒ~An AFU is attached to a port FIU and exposes a fixed length MMIO region to be
used for accelerator-specific control registers.”…””}”(hjK	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj:	  hžhubh¸)”}”(hŒ—User-space applications can acquire exclusive access to an AFU attached to a
port by using open() on the port device node and release it using close().”h]”hŒ—User-space applications can acquire exclusive access to an AFU attached to a
port by using open() on the port device node and release it using close().”…””}”(hjY	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj:	  hžhubh¸)”}”(hŒ3The following functions are exposed through ioctls:”h]”hŒ3The following functions are exposed through ioctls:”…””}”(hjg	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M	hj:	  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hŒ1Get driver API version (DFL_FPGA_GET_API_VERSION)”h]”h¸)”}”(hjz	  h]”hŒ1Get driver API version (DFL_FPGA_GET_API_VERSION)”…””}”(hj|	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjx	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ/Check for extensions (DFL_FPGA_CHECK_EXTENSION)”h]”h¸)”}”(hj‘	  h]”hŒ/Check for extensions (DFL_FPGA_CHECK_EXTENSION)”…””}”(hj“	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ&Get port info (DFL_FPGA_PORT_GET_INFO)”h]”h¸)”}”(hj¨	  h]”hŒ&Get port info (DFL_FPGA_PORT_GET_INFO)”…””}”(hjª	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj¦	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ4Get MMIO region info (DFL_FPGA_PORT_GET_REGION_INFO)”h]”h¸)”}”(hj¿	  h]”hŒ4Get MMIO region info (DFL_FPGA_PORT_GET_REGION_INFO)”…””}”(hjÁ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj½	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ&Map DMA buffer (DFL_FPGA_PORT_DMA_MAP)”h]”h¸)”}”(hjÖ	  h]”hŒ&Map DMA buffer (DFL_FPGA_PORT_DMA_MAP)”…””}”(hjØ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÔ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ*Unmap DMA buffer (DFL_FPGA_PORT_DMA_UNMAP)”h]”h¸)”}”(hjí	  h]”hŒ*Unmap DMA buffer (DFL_FPGA_PORT_DMA_UNMAP)”…””}”(hjï	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjë	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒReset AFU (DFL_FPGA_PORT_RESET)”h]”h¸)”}”(hj
  h]”hŒReset AFU (DFL_FPGA_PORT_RESET)”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ@Get number of irqs of port error (DFL_FPGA_PORT_ERR_GET_IRQ_NUM)”h]”h¸)”}”(hj
  h]”hŒ@Get number of irqs of port error (DFL_FPGA_PORT_ERR_GET_IRQ_NUM)”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ@Set interrupt trigger for port error (DFL_FPGA_PORT_ERR_SET_IRQ)”h]”h¸)”}”(hj2
  h]”hŒ@Set interrupt trigger for port error (DFL_FPGA_PORT_ERR_SET_IRQ)”…””}”(hj4
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj0
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ;Get number of irqs of UINT (DFL_FPGA_PORT_UINT_GET_IRQ_NUM)”h]”h¸)”}”(hjI
  h]”hŒ;Get number of irqs of UINT (DFL_FPGA_PORT_UINT_GET_IRQ_NUM)”…””}”(hjK
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjG
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h NubhÍ)”}”(hŒ<Set interrupt trigger for UINT (DFL_FPGA_PORT_UINT_SET_IRQ)
”h]”h¸)”}”(hŒ;Set interrupt trigger for UINT (DFL_FPGA_PORT_UINT_SET_IRQ)”h]”hŒ;Set interrupt trigger for UINT (DFL_FPGA_PORT_UINT_SET_IRQ)”…””}”(hjb
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj^
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhju	  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j„  uh1hÇhŸh¶h Mhj:	  hžhubj¬  )”}”(hhh]”j±  )”}”(hX  DFL_FPGA_PORT_RESET:
reset the FPGA Port and its AFU. Userspace can do Port
reset at any time, e.g. during DMA or Partial Reconfiguration. But it should
never cause any system level issue, only functional failure (e.g. DMA or PR
operation failure) and be recoverable from the failure.
”h]”(j·  )”}”(hŒDFL_FPGA_PORT_RESET:”h]”hŒDFL_FPGA_PORT_RESET:”…””}”(hjƒ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h Mhj
  ubjÇ  )”}”(hhh]”h¸)”}”(hX  reset the FPGA Port and its AFU. Userspace can do Port
reset at any time, e.g. during DMA or Partial Reconfiguration. But it should
never cause any system level issue, only functional failure (e.g. DMA or PR
operation failure) and be recoverable from the failure.”h]”hX  reset the FPGA Port and its AFU. Userspace can do Port
reset at any time, e.g. during DMA or Partial Reconfiguration. But it should
never cause any system level issue, only functional failure (e.g. DMA or PR
operation failure) and be recoverable from the failure.”…””}”(hj”
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj‘
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h Mhj|
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j«  hj:	  hžhhŸh¶h Nubh¸)”}”(hŒAUser-space applications can also mmap() accelerator MMIO regions.”h]”hŒAUser-space applications can also mmap() accelerator MMIO regions.”…””}”(hj´
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj:	  hžhubh¸)”}”(hŒ[More functions are exposed through sysfs:
(/sys/class/fpga_region/<regionX>/<dfl-port.m>/):”h]”hŒ[More functions are exposed through sysfs:
(/sys/class/fpga_region/<regionX>/<dfl-port.m>/):”…””}”(hjÂ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj:	  hžhubj¦  )”}”(hX  Read Accelerator GUID (afu_id)
    afu_id indicates which PR bitstream is programmed to this AFU.

Error reporting (errors/)
    error reporting sysfs interfaces allow user to read port/afu errors
    detected by the hardware, and clear the logged errors.

”h]”j¬  )”}”(hhh]”(j±  )”}”(hŒ^Read Accelerator GUID (afu_id)
afu_id indicates which PR bitstream is programmed to this AFU.
”h]”(j·  )”}”(hŒRead Accelerator GUID (afu_id)”h]”hŒRead Accelerator GUID (afu_id)”…””}”(hjÛ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h M#hj×
  ubjÇ  )”}”(hhh]”h¸)”}”(hŒ>afu_id indicates which PR bitstream is programmed to this AFU.”h]”hŒ>afu_id indicates which PR bitstream is programmed to this AFU.”…””}”(hjì
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M#hjé
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj×
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h M#hjÔ
  ubj±  )”}”(hŒ–Error reporting (errors/)
error reporting sysfs interfaces allow user to read port/afu errors
detected by the hardware, and clear the logged errors.

”h]”(j·  )”}”(hŒError reporting (errors/)”h]”hŒError reporting (errors/)”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¶  hŸh¶h M(hj  ubjÇ  )”}”(hhh]”h¸)”}”(hŒzerror reporting sysfs interfaces allow user to read port/afu errors
detected by the hardware, and clear the logged errors.”h]”hŒzerror reporting sysfs interfaces allow user to read port/afu errors
detected by the hardware, and clear the logged errors.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M&hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÆ  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j°  hŸh¶h M(hjÔ
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j«  hjÐ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¥  hŸh¶h M"hj:	  hžhubeh}”(h]”Œafu”ah ]”h"]”Œafu”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒDFL Framework Overview”h]”hŒDFL Framework Overview”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjI  hžhhŸh¶h M+ubj³  )”}”(hX         +----------+    +--------+ +--------+ +--------+
       |   FME    |    |  AFU   | |  AFU   | |  AFU   |
       |  Module  |    | Module | | Module | | Module |
       +----------+    +--------+ +--------+ +--------+
               +-----------------------+
               | FPGA Container Device |    Device Feature List
               |  (FPGA Base Region)   |         Framework
               +-----------------------+
------------------------------------------------------------------
             +----------------------------+
             |   FPGA DFL Device Module   |
             | (e.g. PCIE/Platform Device)|
             +----------------------------+
               +------------------------+
               |  FPGA Hardware Device  |
               +------------------------+”h]”hX         +----------+    +--------+ +--------+ +--------+
       |   FME    |    |  AFU   | |  AFU   | |  AFU   |
       |  Module  |    | Module | | Module | | Module |
       +----------+    +--------+ +--------+ +--------+
               +-----------------------+
               | FPGA Container Device |    Device Feature List
               |  (FPGA Base Region)   |         Framework
               +-----------------------+
------------------------------------------------------------------
             +----------------------------+
             |   FPGA DFL Device Module   |
             | (e.g. PCIE/Platform Device)|
             +----------------------------+
               +------------------------+
               |  FPGA Hardware Device  |
               +------------------------+”…””}”hjZ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h M/hjI  hžhubh¸)”}”(hX  DFL framework in kernel provides common interfaces to create container device
(FPGA base region), discover feature devices and their private features from the
given Device Feature Lists and create platform devices for feature devices
(e.g. FME, Port and AFU) with related resources under the container device. It
also abstracts operations for the private features and exposes common ops to
feature device drivers.”h]”hX  DFL framework in kernel provides common interfaces to create container device
(FPGA base region), discover feature devices and their private features from the
given Device Feature Lists and create platform devices for feature devices
(e.g. FME, Port and AFU) with related resources under the container device. It
also abstracts operations for the private features and exposes common ops to
feature device drivers.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M@hjI  hžhubh¸)”}”(hX¾  The FPGA DFL Device could be different hardware, e.g. PCIe device, platform
device and etc. Its driver module is always loaded first once the device is
created by the system. This driver plays an infrastructural role in the
driver architecture. It locates the DFLs in the device memory, handles them
and related resources to common interfaces from DFL framework for enumeration.
(Please refer to drivers/fpga/dfl.c for detailed enumeration APIs).”h]”hX¾  The FPGA DFL Device could be different hardware, e.g. PCIe device, platform
device and etc. Its driver module is always loaded first once the device is
created by the system. This driver plays an infrastructural role in the
driver architecture. It locates the DFLs in the device memory, handles them
and related resources to common interfaces from DFL framework for enumeration.
(Please refer to drivers/fpga/dfl.c for detailed enumeration APIs).”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MGhjI  hžhubh¸)”}”(hŒÖThe FPGA Management Engine (FME) driver is a platform driver which is loaded
automatically after FME platform device creation from the DFL device module. It
provides the key features for FPGA management, including:”h]”hŒÖThe FPGA Management Engine (FME) driver is a platform driver which is loaded
automatically after FME platform device creation from the DFL device module. It
provides the key features for FPGA management, including:”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MNhjI  hžhubj¦  )”}”(hXî  a) Expose static FPGA region information, e.g. version and metadata.
   Users can read related information via sysfs interfaces exposed
   by FME driver.

b) Partial Reconfiguration. The FME driver creates FPGA manager, FPGA
   bridges and FPGA regions during PR sub feature initialization. Once
   it receives a DFL_FPGA_FME_PORT_PR ioctl from user, it invokes the
   common interface function from FPGA Region to complete the partial
   reconfiguration of the PR bitstream to the given port.
”h]”hŒenumerated_list”“”)”}”(hhh]”(hÍ)”}”(hŒ‘Expose static FPGA region information, e.g. version and metadata.
Users can read related information via sysfs interfaces exposed
by FME driver.
”h]”h¸)”}”(hŒExpose static FPGA region information, e.g. version and metadata.
Users can read related information via sysfs interfaces exposed
by FME driver.”h]”hŒExpose static FPGA region information, e.g. version and metadata.
Users can read related information via sysfs interfaces exposed
by FME driver.”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MRhj›  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj˜  ubhÍ)”}”(hXD  Partial Reconfiguration. The FME driver creates FPGA manager, FPGA
bridges and FPGA regions during PR sub feature initialization. Once
it receives a DFL_FPGA_FME_PORT_PR ioctl from user, it invokes the
common interface function from FPGA Region to complete the partial
reconfiguration of the PR bitstream to the given port.
”h]”h¸)”}”(hXC  Partial Reconfiguration. The FME driver creates FPGA manager, FPGA
bridges and FPGA regions during PR sub feature initialization. Once
it receives a DFL_FPGA_FME_PORT_PR ioctl from user, it invokes the
common interface function from FPGA Region to complete the partial
reconfiguration of the PR bitstream to the given port.”h]”hXC  Partial Reconfiguration. The FME driver creates FPGA manager, FPGA
bridges and FPGA regions during PR sub feature initialization. Once
it receives a DFL_FPGA_FME_PORT_PR ioctl from user, it invokes the
common interface function from FPGA Region to complete the partial
reconfiguration of the PR bitstream to the given port.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MVhj³  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj˜  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ
loweralpha”Œprefix”hŒsuffix”Œ)”uh1j–  hj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¥  hŸh¶h MRhjI  hžhubh¸)”}”(hX`  Similar to the FME driver, the FPGA Accelerated Function Unit (AFU) driver is
probed once the AFU platform device is created. The main function of this module
is to provide an interface for userspace applications to access the individual
accelerators, including basic reset control on port, AFU MMIO region export, dma
buffer mapping service functions.”h]”hX`  Similar to the FME driver, the FPGA Accelerated Function Unit (AFU) driver is
probed once the AFU platform device is created. The main function of this module
is to provide an interface for userspace applications to access the individual
accelerators, including basic reset control on port, AFU MMIO region export, dma
buffer mapping service functions.”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M\hjI  hžhubh¸)”}”(hX  After feature platform devices creation, matched platform drivers will be loaded
automatically to handle different functionalities. Please refer to next sections
for detailed information on functional units which have been already implemented
under this DFL framework.”h]”hX  After feature platform devices creation, matched platform drivers will be loaded
automatically to handle different functionalities. Please refer to next sections
for detailed information on functional units which have been already implemented
under this DFL framework.”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MbhjI  hžhubeh}”(h]”Œdfl-framework-overview”ah ]”h"]”Œdfl framework overview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M+ubh¢)”}”(hhh]”(h§)”}”(hŒPartial Reconfiguration”h]”hŒPartial Reconfiguration”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj   hžhhŸh¶h Miubh¸)”}”(hXE  As mentioned above, accelerators can be reconfigured through partial
reconfiguration of a PR bitstream file. The PR bitstream file must have been
generated for the exact static FPGA region and targeted reconfigurable region
(port) of the FPGA, otherwise, the reconfiguration operation will fail and
possibly cause system instability. This compatibility can be checked by
comparing the compatibility ID noted in the header of PR bitstream file against
the compat_id exposed by the target FPGA region. This check is usually done by
userspace before calling the reconfiguration IOCTL.”h]”hXE  As mentioned above, accelerators can be reconfigured through partial
reconfiguration of a PR bitstream file. The PR bitstream file must have been
generated for the exact static FPGA region and targeted reconfigurable region
(port) of the FPGA, otherwise, the reconfiguration operation will fail and
possibly cause system instability. This compatibility can be checked by
comparing the compatibility ID noted in the header of PR bitstream file against
the compat_id exposed by the target FPGA region. This check is usually done by
userspace before calling the reconfiguration IOCTL.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mjhj   hžhubeh}”(h]”Œpartial-reconfiguration”ah ]”h"]”Œpartial reconfiguration”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Miubh¢)”}”(hhh]”(h§)”}”(hŒ FPGA virtualization - PCIe SRIOV”h]”hŒ FPGA virtualization - PCIe SRIOV”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj'  hžhhŸh¶h Muubh¸)”}”(hŒíThis section describes the virtualization support on DFL based FPGA device to
enable accessing an accelerator from applications running in a virtual machine
(VM). This section only describes the PCIe based FPGA device with SRIOV support.”h]”hŒíThis section describes the virtualization support on DFL based FPGA device to
enable accessing an accelerator from applications running in a virtual machine
(VM). This section only describes the PCIe based FPGA device with SRIOV support.”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mvhj'  hžhubh¸)”}”(hŒpFeatures supported by the particular FPGA device are exposed through Device
Feature Lists, as illustrated below:”h]”hŒpFeatures supported by the particular FPGA device are exposed through Device
Feature Lists, as illustrated below:”…””}”(hjF  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mzhj'  hžhubj³  )”}”(hX¸    +-------------------------------+  +-------------+
  |              PF               |  |     VF      |
  +-------------------------------+  +-------------+
      ^            ^         ^              ^
      |            |         |              |
+-----|------------|---------|--------------|-------+
|     |            |         |              |       |
|  +-----+     +-------+ +-------+      +-------+   |
|  | FME |     | Port0 | | Port1 |      | Port2 |   |
|  +-----+     +-------+ +-------+      +-------+   |
|                  ^         ^              ^       |
|                  |         |              |       |
|              +-------+ +------+       +-------+   |
|              |  AFU  | |  AFU |       |  AFU  |   |
|              +-------+ +------+       +-------+   |
|                                                   |
|            DFL based FPGA PCIe Device             |
+---------------------------------------------------+”h]”hX¸    +-------------------------------+  +-------------+
  |              PF               |  |     VF      |
  +-------------------------------+  +-------------+
      ^            ^         ^              ^
      |            |         |              |
+-----|------------|---------|--------------|-------+
|     |            |         |              |       |
|  +-----+     +-------+ +-------+      +-------+   |
|  | FME |     | Port0 | | Port1 |      | Port2 |   |
|  +-----+     +-------+ +-------+      +-------+   |
|                  ^         ^              ^       |
|                  |         |              |       |
|              +-------+ +------+       +-------+   |
|              |  AFU  | |  AFU |       |  AFU  |   |
|              +-------+ +------+       +-------+   |
|                                                   |
|            DFL based FPGA PCIe Device             |
+---------------------------------------------------+”…””•WŒ      }”hjT  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h Mhj'  hžhubh¸)”}”(hŒ:FME is always accessed through the physical function (PF).”h]”hŒ:FME is always accessed through the physical function (PF).”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M’hj'  hžhubh¸)”}”(hX!  Ports (and related AFUs) are accessed via PF by default, but could be exposed
through virtual function (VF) devices via PCIe SRIOV. Each VF only contains
1 Port and 1 AFU for isolation. Users could assign individual VFs (accelerators)
created via PCIe SRIOV interface, to virtual machines.”h]”hX!  Ports (and related AFUs) are accessed via PF by default, but could be exposed
through virtual function (VF) devices via PCIe SRIOV. Each VF only contains
1 Port and 1 AFU for isolation. Users could assign individual VFs (accelerators)
created via PCIe SRIOV interface, to virtual machines.”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M”hj'  hžhubh¸)”}”(hŒGThe driver organization in virtualization case is illustrated below:
::”h]”hŒDThe driver organization in virtualization case is illustrated below:”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M™hj'  hžhubj³  )”}”(hXÖ   +-------++------++------+             |
 | FME   || FME  || FME  |             |
 | FPGA  || FPGA || FPGA |             |
 |Manager||Bridge||Region|             |
 +-------++------++------+             |
 +-----------------------+  +--------+ |             +--------+
 |          FME          |  |  AFU   | |             |  AFU   |
 |         Module        |  | Module | |             | Module |
 +-----------------------+  +--------+ |             +--------+
       +-----------------------+       |       +-----------------------+
       | FPGA Container Device |       |       | FPGA Container Device |
       |  (FPGA Base Region)   |       |       |  (FPGA Base Region)   |
       +-----------------------+       |       +-----------------------+
         +------------------+          |         +------------------+
         | FPGA PCIE Module |          | Virtual | FPGA PCIE Module |
         +------------------+   Host   | Machine +------------------+
-------------------------------------- | ------------------------------
          +---------------+            |          +---------------+
          | PCI PF Device |            |          | PCI VF Device |
          +---------------+            |          +---------------+”h]”hXÖ   +-------++------++------+             |
 | FME   || FME  || FME  |             |
 | FPGA  || FPGA || FPGA |             |
 |Manager||Bridge||Region|             |
 +-------++------++------+             |
 +-----------------------+  +--------+ |             +--------+
 |          FME          |  |  AFU   | |             |  AFU   |
 |         Module        |  | Module | |             | Module |
 +-----------------------+  +--------+ |             +--------+
       +-----------------------+       |       +-----------------------+
       | FPGA Container Device |       |       | FPGA Container Device |
       |  (FPGA Base Region)   |       |       |  (FPGA Base Region)   |
       +-----------------------+       |       +-----------------------+
         +------------------+          |         +------------------+
         | FPGA PCIE Module |          | Virtual | FPGA PCIE Module |
         +------------------+   Host   | Machine +------------------+
-------------------------------------- | ------------------------------
          +---------------+            |          +---------------+
          | PCI PF Device |            |          | PCI VF Device |
          +---------------+            |          +---------------+”…””}”hjŒ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h Mœhj'  hžhubh¸)”}”(hŒaFPGA PCIe device driver is always loaded first once an FPGA PCIe PF or VF device
is detected. It:”h]”hŒaFPGA PCIe device driver is always loaded first once an FPGA PCIe PF or VF device
is detected. It:”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M±hj'  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hŒcFinishes enumeration on both FPGA PCIe PF and VF device using common
interfaces from DFL framework.”h]”h¸)”}”(hŒcFinishes enumeration on both FPGA PCIe PF and VF device using common
interfaces from DFL framework.”h]”hŒcFinishes enumeration on both FPGA PCIe PF and VF device using common
interfaces from DFL framework.”…””}”(hj¯  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M´hj«  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj¨  hžhhŸh¶h NubhÍ)”}”(hŒSupports SRIOV.
”h]”h¸)”}”(hŒSupports SRIOV.”h]”hŒSupports SRIOV.”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M¶hjÃ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj¨  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h M´hj'  hžhubh¸)”}”(hŒúThe FME device driver plays a management role in this driver architecture, it
provides ioctls to release Port from PF and assign Port to PF. After release
a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
sysfs interface.”h]”hŒüThe FME device driver plays a management role in this driver architecture, it
provides ioctls to release Port from PF and assign Port to PF. After release
a port from PF, then itâ€™s safe to expose this port through a VF via PCIe SRIOV
sysfs interface.”…””}”(hjá  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M¸hj'  hžhubh¸)”}”(hŒ—To enable accessing an accelerator from applications running in a VM, the
respective AFU's port needs to be assigned to a VF using the following steps:”h]”hŒ™To enable accessing an accelerator from applications running in a VM, the
respective AFUâ€™s port needs to be assigned to a VF using the following steps:”…””}”(hjï  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M½hj'  hžhubj—  )”}”(hhh]”(hÍ)”}”(hŒ©The PF owns all AFU ports by default. Any port that needs to be
reassigned to a VF must first be released through the
DFL_FPGA_FME_PORT_RELEASE ioctl on the FME device.
”h]”h¸)”}”(hŒ¨The PF owns all AFU ports by default. Any port that needs to be
reassigned to a VF must first be released through the
DFL_FPGA_FME_PORT_RELEASE ioctl on the FME device.”h]”hŒ¨The PF owns all AFU ports by default. Any port that needs to be
reassigned to a VF must first be released through the
DFL_FPGA_FME_PORT_RELEASE ioctl on the FME device.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÀhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjý  hžhhŸh¶h NubhÍ)”}”(hŒ°Once N ports are released from PF, then user can use command below
to enable SRIOV and VFs. Each VF owns only one Port with AFU.

::

   echo N > $PCI_DEVICE_PATH/sriov_numvfs
”h]”(h¸)”}”(hŒ€Once N ports are released from PF, then user can use command below
to enable SRIOV and VFs. Each VF owns only one Port with AFU.”h]”hŒ€Once N ports are released from PF, then user can use command below
to enable SRIOV and VFs. Each VF owns only one Port with AFU.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÄhj  ubj³  )”}”(hŒ&echo N > $PCI_DEVICE_PATH/sriov_numvfs”h]”hŒ&echo N > $PCI_DEVICE_PATH/sriov_numvfs”…””}”hj*  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h MÉhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjý  hžhhŸh¶h NubhÍ)”}”(hŒPass through the VFs to VMs
”h]”h¸)”}”(hŒPass through the VFs to VMs”h]”hŒPass through the VFs to VMs”…””}”(hjB  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MËhj>  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjý  hžhhŸh¶h NubhÍ)”}”(hŒ^The AFU under VF is accessible from applications in VM (using the
same driver inside the VF).
”h]”h¸)”}”(hŒ]The AFU under VF is accessible from applications in VM (using the
same driver inside the VF).”h]”hŒ]The AFU under VF is accessible from applications in VM (using the
same driver inside the VF).”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÍhjV  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjý  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jÑ  Œarabic”jÓ  hjÔ  Œ.”uh1j–  hj'  hžhhŸh¶h MÀubh¸)”}”(hŒqNote that an FME can't be assigned to a VF, thus PR and other management
functions are only available via the PF.”h]”hŒsNote that an FME canâ€™t be assigned to a VF, thus PR and other management
functions are only available via the PF.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÐhj'  hžhubeh}”(h]”Œfpga-virtualization-pcie-sriov”ah ]”h"]”Œ fpga virtualization - pcie sriov”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Muubh¢)”}”(hhh]”(h§)”}”(hŒDevice enumeration”h]”hŒDevice enumeration”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjŒ  hžhhŸh¶h MÔubh¸)”}”(hŒyThis section introduces how applications enumerate the fpga device from
the sysfs hierarchy under /sys/class/fpga_region.”h]”hŒyThis section introduces how applications enumerate the fpga device from
the sysfs hierarchy under /sys/class/fpga_region.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÕhjŒ  hžhubh¸)”}”(hŒ~In the example below, two DFL based FPGA devices are installed in the host. Each
fpga device has one FME and two ports (AFUs).”h]”hŒ~In the example below, two DFL based FPGA devices are installed in the host. Each
fpga device has one FME and two ports (AFUs).”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MØhjŒ  hžhubh¸)”}”(hŒ8FPGA regions are created under /sys/class/fpga_region/::”h]”hŒ7FPGA regions are created under /sys/class/fpga_region/:”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÛhjŒ  hžhubj³  )”}”(hŒ`/sys/class/fpga_region/region0
/sys/class/fpga_region/region1
/sys/class/fpga_region/region2
...”h]”hŒ`/sys/class/fpga_region/region0
/sys/class/fpga_region/region1
/sys/class/fpga_region/region2
...”…””}”hjÇ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h MÝhjŒ  hžhubh¸)”}”(hŒºApplication needs to search each regionX folder, if feature device is found,
(e.g. "dfl-port.n" or "dfl-fme.m" is found), then it's the base
fpga region which represents the FPGA device.”h]”hŒÄApplication needs to search each regionX folder, if feature device is found,
(e.g. â€œdfl-port.nâ€ or â€œdfl-fme.mâ€ is found), then itâ€™s the base
fpga region which represents the FPGA device.”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MâhjŒ  hžhubh¸)”}”(hŒDEach base region has one FME and two ports (AFUs) as child devices::”h]”hŒCEach base region has one FME and two ports (AFUs) as child devices:”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MæhjŒ  hžhubj³  )”}”(hX  /sys/class/fpga_region/region0/dfl-fme.0
/sys/class/fpga_region/region0/dfl-port.0
/sys/class/fpga_region/region0/dfl-port.1
...

/sys/class/fpga_region/region3/dfl-fme.1
/sys/class/fpga_region/region3/dfl-port.2
/sys/class/fpga_region/region3/dfl-port.3
...”h]”hX  /sys/class/fpga_region/region0/dfl-fme.0
/sys/class/fpga_region/region0/dfl-port.0
/sys/class/fpga_region/region0/dfl-port.1
...

/sys/class/fpga_region/region3/dfl-fme.1
/sys/class/fpga_region/region3/dfl-port.2
/sys/class/fpga_region/region3/dfl-port.3
...”…””}”hjñ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h MèhjŒ  hžhubh¸)”}”(hŒ?In general, the FME/AFU sysfs interfaces are named as follows::”h]”hŒ>In general, the FME/AFU sysfs interfaces are named as follows:”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MòhjŒ  hžhubj³  )”}”(hŒ\/sys/class/fpga_region/<regionX>/<dfl-fme.n>/
/sys/class/fpga_region/<regionX>/<dfl-port.m>/”h]”hŒ\/sys/class/fpga_region/<regionX>/<dfl-fme.n>/
/sys/class/fpga_region/<regionX>/<dfl-port.m>/”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h MôhjŒ  hžhubh¸)”}”(hŒTwith 'n' consecutively numbering all FMEs and 'm' consecutively numbering all
ports.”h]”hŒ\with â€˜nâ€™ consecutively numbering all FMEs and â€˜mâ€™ consecutively numbering all
ports.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M÷hjŒ  hžhubh¸)”}”(hŒGThe device nodes used for ioctl() or mmap() can be referenced through::”h]”hŒFThe device nodes used for ioctl() or mmap() can be referenced through:”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MúhjŒ  hžhubj³  )”}”(hŒb/sys/class/fpga_region/<regionX>/<dfl-fme.n>/dev
/sys/class/fpga_region/<regionX>/<dfl-port.n>/dev”h]”hŒb/sys/class/fpga_region/<regionX>/<dfl-fme.n>/dev
/sys/class/fpga_region/<regionX>/<dfl-port.n>/dev”…””}”hj7  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h MühjŒ  hžhubeh}”(h]”Œdevice-enumeration”ah ]”h"]”Œdevice enumeration”ah$]”h&]”uh1h¡hh£hžhhŸh¶h MÔubh¢)”}”(hhh]”(h§)”}”(hŒPerformance Counters”h]”hŒPerformance Counters”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjM  hžhhŸh¶h Mubh¸)”}”(hX£  Performance reporting is one private feature implemented in FME. It could
supports several independent, system-wide, device counter sets in hardware to
monitor and count for performance events, including "basic", "cache", "fabric",
"vtd" and "vtd_sip" counters. Users could use standard perf tool to monitor
FPGA cache hit/miss rate, transaction number, interface clock counter of AFU
and other FPGA performance events.”h]”hX·  Performance reporting is one private feature implemented in FME. It could
supports several independent, system-wide, device counter sets in hardware to
monitor and count for performance events, including â€œbasicâ€, â€œcacheâ€, â€œfabricâ€,
â€œvtdâ€ and â€œvtd_sipâ€ counters. Users could use standard perf tool to monitor
FPGA cache hit/miss rate, transaction number, interface clock counter of AFU
and other FPGA performance events.”…””}”(hj^  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjM  hžhubh¸)”}”(hŒêDifferent FPGA devices may have different counter sets, depending on hardware
implementation. E.g., some discrete FPGA cards don't have any cache. User could
use "perf list" to check which perf events are supported by target hardware.”h]”hŒðDifferent FPGA devices may have different counter sets, depending on hardware
implementation. E.g., some discrete FPGA cards donâ€™t have any cache. User could
use â€œperf listâ€ to check which perf events are supported by target hardware.”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M	hjM  hžhubh¸)”}”(hŒôIn order to allow user to use standard perf API to access these performance
counters, driver creates a perf PMU, and related sysfs interfaces in
/sys/bus/event_source/devices/dfl_fme* to describe available perf events and
configuration options.”h]”hŒôIn order to allow user to use standard perf API to access these performance
counters, driver creates a perf PMU, and related sysfs interfaces in
/sys/bus/event_source/devices/dfl_fme* to describe available perf events and
configuration options.”…””}”(hjz  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjM  hžhubh¸)”}”(hXO  The "format" directory describes the format of the config field of struct
perf_event_attr. There are 3 bitfields for config: "evtype" defines which type
the perf event belongs to; "event" is the identity of the event within its
category; "portid" is introduced to decide counters set to monitor on FPGA
overall data or a specific port.”h]”hX_  The â€œformatâ€ directory describes the format of the config field of struct
perf_event_attr. There are 3 bitfields for config: â€œevtypeâ€ defines which type
the perf event belongs to; â€œeventâ€ is the identity of the event within its
category; â€œportidâ€ is introduced to decide counters set to monitor on FPGA
overall data or a specific port.”…””}”(hjˆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjM  hžhubh¸)”}”(hXX  The "events" directory describes the configuration templates for all available
events which can be used with perf tool directly. For example, fab_mmio_read
has the configuration "event=0x06,evtype=0x02,portid=0xff", which shows this
event belongs to fabric type (0x02), the local event id is 0x06 and it is for
overall monitoring (portid=0xff).”h]”hX`  The â€œeventsâ€ directory describes the configuration templates for all available
events which can be used with perf tool directly. For example, fab_mmio_read
has the configuration â€œevent=0x06,evtype=0x02,portid=0xffâ€, which shows this
event belongs to fabric type (0x02), the local event id is 0x06 and it is for
overall monitoring (portid=0xff).”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjM  hžhubh¸)”}”(hŒExample usage of perf::”h]”hŒExample usage of perf:”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjM  hžhubj³  )”}”(hXt  $# perf list |grep dfl_fme

dfl_fme0/fab_mmio_read/                              [Kernel PMU event]
<...>
dfl_fme0/fab_port_mmio_read,portid=?/                [Kernel PMU event]
<...>

$# perf stat -a -e dfl_fme0/fab_mmio_read/ <command>
or
$# perf stat -a -e dfl_fme0/event=0x06,evtype=0x02,portid=0xff/ <command>
or
$# perf stat -a -e dfl_fme0/config=0xff2006/ <command>”h]”hXt  $# perf list |grep dfl_fme

dfl_fme0/fab_mmio_read/                              [Kernel PMU event]
<...>
dfl_fme0/fab_port_mmio_read,portid=?/                [Kernel PMU event]
<...>

$# perf stat -a -e dfl_fme0/fab_mmio_read/ <command>
or
$# perf stat -a -e dfl_fme0/event=0x06,evtype=0x02,portid=0xff/ <command>
or
$# perf stat -a -e dfl_fme0/config=0xff2006/ <command>”…””}”hj²  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h M hjM  hžhubh¸)”}”(hŒ³Another example, fab_port_mmio_read monitors mmio read of a specific port. So
its configuration template is "event=0x06,evtype=0x01,portid=?". The portid
should be explicitly set.”h]”hŒ·Another example, fab_port_mmio_read monitors mmio read of a specific port. So
its configuration template is â€œevent=0x06,evtype=0x01,portid=?â€. The portid
should be explicitly set.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M-hjM  hžhubh¸)”}”(hŒIts usage of perf::”h]”hŒIts usage of perf:”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M1hjM  hžhubj³  )”}”(hŒÈ$# perf stat -a -e dfl_fme0/fab_port_mmio_read,portid=0x0/ <command>
or
$# perf stat -a -e dfl_fme0/event=0x06,evtype=0x02,portid=0x0/ <command>
or
$# perf stat -a -e dfl_fme0/config=0x2006/ <command>”h]”hŒÈ$# perf stat -a -e dfl_fme0/fab_port_mmio_read,portid=0x0/ <command>
or
$# perf stat -a -e dfl_fme0/event=0x06,evtype=0x02,portid=0x0/ <command>
or
$# perf stat -a -e dfl_fme0/config=0x2006/ <command>”…””}”hjÜ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h M3hjM  hžhubh¸)”}”(hX6  Please note for fabric counters, overall perf events (fab_*) and port perf
events (fab_port_*) actually share one set of counters in hardware, so it can't
monitor both at the same time. If this set of counters is configured to monitor
overall data, then per port perf data is not supported. See below example::”h]”hX7  Please note for fabric counters, overall perf events (fab_*) and port perf
events (fab_port_*) actually share one set of counters in hardware, so it canâ€™t
monitor both at the same time. If this set of counters is configured to monitor
overall data, then per port perf data is not supported. See below example:”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M9hjM  hžhubj³  )”}”(hXM  $# perf stat -e dfl_fme0/fab_mmio_read/,dfl_fme0/fab_port_mmio_write,\
                                                  portid=0/ sleep 1

Performance counter stats for 'system wide':

               3      dfl_fme0/fab_mmio_read/
 <not supported>      dfl_fme0/fab_port_mmio_write,portid=0x0/

     1.001750904 seconds time elapsed”h]”hXM  $# perf stat -e dfl_fme0/fab_mmio_read/,dfl_fme0/fab_port_mmio_write,\
                                                  portid=0/ sleep 1

Performance counter stats for 'system wide':

               3      dfl_fme0/fab_mmio_read/
 <not supported>      dfl_fme0/fab_port_mmio_write,portid=0x0/

     1.001750904 seconds time elapsed”…””}”hjø  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h M>hjM  hžhubh¸)”}”(hŒÒThe driver also provides a "cpumask" sysfs attribute, which contains only one
CPU id used to access these perf events. Counting on multiple CPU is not allowed
since they are system-wide counters on FPGA device.”h]”hŒÖThe driver also provides a â€œcpumaskâ€ sysfs attribute, which contains only one
CPU id used to access these perf events. Counting on multiple CPU is not allowed
since they are system-wide counters on FPGA device.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MHhjM  hžhubh¸)”}”(hŒNThe current driver does not support sampling. So "perf record" is unsupported.”h]”hŒRThe current driver does not support sampling. So â€œperf recordâ€ is unsupported.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MLhjM  hžhubeh}”(h]”Œperformance-counters”ah ]”h"]”Œperformance counters”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒInterrupt support”h]”hŒInterrupt support”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj*  hžhhŸh¶h MPubh¸)”}”(hX4  Some FME and AFU private features are able to generate interrupts. As mentioned
above, users could call ioctl (DFL_FPGA_*_GET_IRQ_NUM) to know whether or how
many interrupts are supported for this private feature. Drivers also implement
an eventfd based interrupt handling mechanism for users to get notified when
interrupt happens. Users could set eventfds to driver via
ioctl (DFL_FPGA_*_SET_IRQ), and then poll/select on these eventfds waiting for
notification.
In Current DFL, 3 sub features (Port error, FME global error and AFU interrupt)
support interrupts.”h]”hX4  Some FME and AFU private features are able to generate interrupts. As mentioned
above, users could call ioctl (DFL_FPGA_*_GET_IRQ_NUM) to know whether or how
many interrupts are supported for this private feature. Drivers also implement
an eventfd based interrupt handling mechanism for users to get notified when
interrupt happens. Users could set eventfds to driver via
ioctl (DFL_FPGA_*_SET_IRQ), and then poll/select on these eventfds waiting for
notification.
In Current DFL, 3 sub features (Port error, FME global error and AFU interrupt)
support interrupts.”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MQhj*  hžhubeh}”(h]”Œinterrupt-support”ah ]”h"]”Œinterrupt support”ah$]”h&]”uh1h¡hh£hžhhŸh¶h MPubh¢)”}”(hhh]”(h§)”}”(hŒAdd new FIUs support”h]”hŒAdd new FIUs support”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjQ  hžhhŸh¶h M]ubh¸)”}”(hX§  It's possible that developers made some new function blocks (FIUs) under this
DFL framework, then new platform device driver needs to be developed for the
new feature dev (FIU) following the same way as existing feature dev drivers
(e.g. FME and Port/AFU platform device driver). Besides that, it requires
modification on DFL framework enumeration code too, for new FIU type detection
and related platform devices creation.”h]”hX©  Itâ€™s possible that developers made some new function blocks (FIUs) under this
DFL framework, then new platform device driver needs to be developed for the
new feature dev (FIU) following the same way as existing feature dev drivers
(e.g. FME and Port/AFU platform device driver). Besides that, it requires
modification on DFL framework enumeration code too, for new FIU type detection
and related platform devices creation.”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M^hjQ  hžhubeh}”(h]”Œadd-new-fius-support”ah ]”h"]”Œadd new fius support”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M]ubh¢)”}”(hhh]”(h§)”}”(hŒ Add new private features support”h]”hŒ Add new private features support”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjx  hžhhŸh¶h Mgubh¸)”}”(hXæ  In some cases, we may need to add some new private features to existing FIUs
(e.g. FME or Port). Developers don't need to touch enumeration code in DFL
framework, as each private feature will be parsed automatically and related
mmio resources can be found under FIU platform device created by DFL framework.
Developer only needs to provide a sub feature driver with matched feature id.
FME Partial Reconfiguration Sub Feature driver (see drivers/fpga/dfl-fme-pr.c)
could be a reference.”h]”hXè  In some cases, we may need to add some new private features to existing FIUs
(e.g. FME or Port). Developers donâ€™t need to touch enumeration code in DFL
framework, as each private feature will be parsed automatically and related
mmio resources can be found under FIU platform device created by DFL framework.
Developer only needs to provide a sub feature driver with matched feature id.
FME Partial Reconfiguration Sub Feature driver (see drivers/fpga/dfl-fme-pr.c)
could be a reference.”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhhjx  hžhubh¸)”}”(hŒ‰Please refer to below link to existing feature id table and guide for new feature
ids application.
https://github.com/OPAE/dfl-feature-id”h]”(hŒcPlease refer to below link to existing feature id table and guide for new feature
ids application.
”…””}”(hj—  hžhhŸNh NubhÚ)”}”(hŒ&https://github.com/OPAE/dfl-feature-id”h]”hŒ&https://github.com/OPAE/dfl-feature-id”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¡  uh1hÙhj—  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mphjx  hžhubeh}”(h]”Œ add-new-private-features-support”ah ]”h"]”Œ add new private features support”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mgubh¢)”}”(hhh]”(h§)”}”(hŒ Location of DFLs on a PCI Device”h]”hŒ Location of DFLs on a PCI Device”…””}”(hj¿  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj¼  hžhhŸh¶h Mvubh¸)”}”(hXõ  The original method for finding a DFL on a PCI device assumed the start of the
first DFL to offset 0 of bar 0.  If the first node of the DFL is an FME,
then further DFLs in the port(s) are specified in FME header registers.
Alternatively, a PCIe vendor specific capability structure can be used to
specify the location of all the DFLs on the device, providing flexibility
for the type of starting node in the DFL.  Intel has reserved the
VSEC ID of 0x43 for this purpose.  The vendor specific
data begins with a 4 byte vendor specific register for the number of DFLs followed 4 byte
Offset/BIR vendor specific registers for each DFL. Bits 2:0 of Offset/BIR register
indicates the BAR, and bits 31:3 form the 8 byte aligned offset where bits 2:0 are
zero.
::”h]”hXò  The original method for finding a DFL on a PCI device assumed the start of the
first DFL to offset 0 of bar 0.  If the first node of the DFL is an FME,
then further DFLs in the port(s) are specified in FME header registers.
Alternatively, a PCIe vendor specific capability structure can be used to
specify the location of all the DFLs on the device, providing flexibility
for the type of starting node in the DFL.  Intel has reserved the
VSEC ID of 0x43 for this purpose.  The vendor specific
data begins with a 4 byte vendor specific register for the number of DFLs followed 4 byte
Offset/BIR vendor specific registers for each DFL. Bits 2:0 of Offset/BIR register
indicates the BAR, and bits 31:3 form the 8 byte aligned offset where bits 2:0 are
zero.”…””}”(hjÍ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mwhj¼  hžhubj³  )”}”(hX  +----------------------------+
|31     Number of DFLS      0|
+----------------------------+
|31     Offset     3|2 BIR  0|
+----------------------------+
              . . .
+----------------------------+
|31     Offset     3|2 BIR  0|
+----------------------------+”h]”hX  +----------------------------+
|31     Number of DFLS      0|
+----------------------------+
|31     Offset     3|2 BIR  0|
+----------------------------+
              . . .
+----------------------------+
|31     Offset     3|2 BIR  0|
+----------------------------+”…””}”hjÛ  sbah}”(h]”h ]”h"]”h$]”h&]”jÂ  jÃ  uh1j²  hŸh¶h M„hj¼  hžhubh¸)”}”(hŒâBeing able to specify more than one DFL per BAR has been considered, but it
was determined the use case did not provide value.  Specifying a single DFL
per BAR simplifies the implementation and allows for extra error checking.”h]”hŒâBeing able to specify more than one DFL per BAR has been considered, but it
was determined the use case did not provide value.  Specifying a single DFL
per BAR simplifies the implementation and allows for extra error checking.”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MŽhj¼  hžhubeh}”(h]”Œ location-of-dfls-on-a-pci-device”ah ]”h"]”Œ location of dfls on a pci device”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mvubh¢)”}”(hhh]”(h§)”}”(hŒ(Userspace driver support for DFL devices”h]”hŒ(Userspace driver support for DFL devices”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÿ  hžhhŸh¶h M”ubh¸)”}”(hX  The purpose of an FPGA is to be reprogrammed with newly developed hardware
components. New hardware can instantiate a new private feature in the DFL, and
then present a DFL device in the system. In some cases users may need a
userspace driver for the DFL device:”h]”hX  The purpose of an FPGA is to be reprogrammed with newly developed hardware
components. New hardware can instantiate a new private feature in the DFL, and
then present a DFL device in the system. In some cases users may need a
userspace driver for the DFL device:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M•hjÿ  hžhubhÈ)”}”(hhh]”(hÍ)”}”(hŒ>Users may need to run some diagnostic test for their hardware.”h]”h¸)”}”(hj#  h]”hŒ>Users may need to run some diagnostic test for their hardware.”…””}”(hj%  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mšhj!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸh¶h NubhÍ)”}”(hŒ4Users may prototype the kernel driver in user space.”h]”h¸)”}”(hj:  h]”hŒ4Users may prototype the kernel driver in user space.”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M›hj8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸh¶h NubhÍ)”}”(hŒmSome hardware is designed for specific purposes and does not fit into one of
the standard kernel subsystems.
”h]”h¸)”}”(hŒlSome hardware is designed for specific purposes and does not fit into one of
the standard kernel subsystems.”h]”hŒlSome hardware is designed for specific purposes and does not fit into one of
the standard kernel subsystems.”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MœhjO  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jƒ  j   uh1hÇhŸh¶h Mšhjÿ  hžhubh¸)”}”(hŒ—This requires direct access to MMIO space and interrupt handling from
userspace. The uio_dfl module exposes the UIO device interfaces for this
purpose.”h]”hŒ—This requires direct access to MMIO space and interrupt handling from
userspace. The uio_dfl module exposes the UIO device interfaces for this
purpose.”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MŸhjÿ  hžhubh¸)”}”(hŒœCurrently the uio_dfl driver only supports the Ether Group sub feature, which
has no irq in hardware. So the interrupt handling is not added in this driver.”h]”hŒœCurrently the uio_dfl driver only supports the Ether Group sub feature, which
has no irq in hardware. So the interrupt handling is not added in this driver.”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M£hjÿ  hžhubh¸)”}”(hŒ¬UIO_DFL should be selected to enable the uio_dfl module driver. To support a
new DFL feature via UIO direct access, its feature id should be added to the
driver's id_table.”h]”hŒ®UIO_DFL should be selected to enable the uio_dfl module driver. To support a
new DFL feature via UIO direct access, its feature id should be added to the
driverâ€™s id_table.”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M¦hjÿ  hžhubeh}”(h]”Œ(userspace-driver-support-for-dfl-devices”ah ]”h"]”Œ(userspace driver support for dfl devices”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M”ubh¢)”}”(hhh]”(h§)”}”(hŒOpen discussion”h]”hŒOpen discussion”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjŸ  hžhhŸh¶h M¬ubh¸)”}”(hŒÜFME driver exports one ioctl (DFL_FPGA_FME_PORT_PR) for partial reconfiguration
to user now. In the future, if unified user interfaces for reconfiguration are
added, FME driver should switch to them from ioctl interface.”h]”hŒÜFME driver exports one ioctl (DFL_FPGA_FME_PORT_PR) for partial reconfiguration
to user now. In the future, if unified user interfaces for reconfiguration are
added, FME driver should switch to them from ioctl interface.”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M­hjŸ  hžhubeh}”(h]”Œopen-discussion”ah ]”h"]”Œopen discussion”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M¬ubeh}”(h]”Œ/fpga-device-feature-list-dfl-framework-overview”ah ]”h"]”Œ1fpga device feature list (dfl) framework overview”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jñ  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jË  jÈ  j  j  j„  j  j®  j«  j	  j	  j7	  j4	  jF  jC  jý  jú  j$  j!  j‰  j†  jJ  jG  j'  j$  jN  jK  ju  jr  j¹  j¶  jü  jù  jœ  j™  jÃ  jÀ  uŒ	nametypes”}”(jË  ‰j  ‰j„  ‰j®  ‰j	  ‰j7	  ‰jF  ‰jý  ‰j$  ‰j‰  ‰jJ  ‰j'  ‰jN  ‰ju  ‰j¹  ‰jü  ‰jœ  ‰jÃ  ‰uh}”(jÈ  h£j  j“  j  j  j«  j‡  j	  j±  j4	  j	  jC  j:	  jú  jI  j!  j   j†  j'  jG  jŒ  j$  jM  jK  j*  jr  jQ  j¶  jx  jù  j¼  j™  jÿ  jÀ  jŸ  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”hŒsystem_message”“”)”}”(hhh]”h¸)”}”(hŒfPossible title underline, too short for the title.
Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hjU  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”MšŒsource”h¶uh1jS  hj'  hžhhŸh¶h MšubaŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.