You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Redirecting to <ahref="../../../../../../../rel-24.2/embedded-designs/agilex-7/f-series/soc/rsu/ug-rsu-multiqspi-agx7f-soc/">../../../../../../../rel-24.2/embedded-designs/agilex-7/f-series/soc/rsu/ug-rsu-multiqspi-agx7f-soc/</a>...
Agilex™ 7 SoC HPS Multi-QSPI Remote System Update Example
1603
+
</a>
1604
+
</li>
1605
+
1606
+
1607
+
1608
+
1593
1609
</ul>
1594
1610
</nav>
1595
1611
</li>
@@ -1726,18 +1742,12 @@
1726
1742
1727
1743
1728
1744
1729
-
<!--This template provides an outline for you to create your Linux driver page. Below each guidance comment there is an example for your to reference.-->
<p>This set of drivers is designed to support FME functionality, as implemented under FPGA Device Feature List (DFL) framework. It is used to expose FME capabilities.</p>
1740
-
<!--If this is an OFS Driver include this table that notes the driver, what it maps to, the source and whether the driver is optional or not for DFL.-->
<!--If there are multiple drivers, you can create a driver dependency chart using mermaid. Below is an example; to learn more about mermaid see https://mermaid.js.org/ -->
1778
1787
<preclass="mermaid"><code>graph TD;
1779
1788
A[dfl-fme]-->B[dfl-fme-mgr];
1780
1789
A[dfl-fme]-->C[dfl-fme-br];
1781
1790
A[dfl-fme]-->D[dfl-fme-region]; </code></pre>
1782
-
<!--Describe the IP(s) that the driver controls, provide a block diagram and link to any user guide documentation. -->
<p>The FPGA Management Engine IP provides management features for the platform and controls reset and loading of the AFU into the partial reconfiguration region of the FPGA. Implementation of a PR region is optional.</p>
1785
1793
<p>Each FME feature exposes its capability to host software drivers through a device feature header (DFH) register found at the beginning of its control status register (CSR) space. The FME CSR maps to physical function 0 (PF0) Base address register 0 (BAR0) so that software can access it through a single PCIe link. For more information about DFHs, refer to the <ahref="https://ofs.github.io/latest/hw/d5005/reference_manuals/ofs_fim/mnl_fim_ofs_d5005/#721-device-feature-header-dfh-structure">Device Feature Header (DFH) structure</a>.</p>
<p>The source code for these drivers can be found at https://github.com/OFS/linux-dfl/tree/master/drivers/fpga, where branches labelled fpga-ofs-dev-*-lts correspond with the latest developmental versions of the DFL driver suite on that specific kernel version.</p>
<p>This driver set is a DFL specific implementation of generic FPGA drivers available in the kernel. <code>dfl-fme-mgr</code> is a DFL specific instantiation of the generic FPGA manager (drivers/linux/fpga/fpga-mgr.c), <code>dfl-fme-br</code> builds on top of a generic FPGA bridge (drivers/fpga/fpga-bridge.c), and <code>dfl-fme-region</code> instantiates an FPGA region. All three supplementary DFL Drivers depend on <code>dfl-fme</code>.</p>
1792
1798
<p>The DFL FME driver is a feature device implemented under the Device Feature List (DFL) framework. It enables the platform driver for the FME IP and implements all FPGA platform level management features. Only one FME is created per DFL based FPGA device. The DFL Bridge, Manager, and Region drivers are only required when attempting to configure a PR region in the FIM.</p>
<p>The FPGA Management Engine IP is included as a part of the FIM design for <ahref="https://github.com/OFS/ofs-agx7-pcie-attach">PCIe Attach supporting DFL</a>, <ahref="https://github.com/OFS/ofs-d5005.git">Stratix 10 PCIe Attach</a>, and <ahref="https://github.com/OFS/ofs-f2000x-pl">SoC Attach</a>. Please refer to <ahref="https://ofs.github.io/">site</a> for more information about these designs.</p>
1809
1812
@@ -1812,7 +1815,7 @@ <h2 id="example-designs"><strong>Example Designs</strong><a class="headerlink" h
Agilex™ 7 SoC HPS Multi-QSPI Remote System Update Example
1598
+
</a>
1599
+
</li>
1600
+
1601
+
1602
+
1603
+
1588
1604
</ul>
1589
1605
</nav>
1590
1606
</li>
@@ -1723,19 +1739,14 @@
1723
1739
1724
1740
<h1>Links</h1>
1725
1741
1726
-
<!--This file is used for listing global document links. Create a live link when you want to share it across collateral to ensure the naming of the file is always the same. Share your agreed upon bracketed document name with others in this link file and whenever it is listed in their .md file, the correct active links will be created on the site. This links.md also helps if the link path changes, so you don't have to go back and change all of your documentation. Steps to get this to work are:
1727
-
1. Decide on document name.
1728
-
2. Decide where your link should go. If it is a global document name put it in the docs_module folder. If it is a interdocument link within a certain folder such as "embedded-designs" then create a links.md in the top folder, such as /docs/embedded-designs/doc_modules/links.md and place your link there.
1729
-
3. Format the links as such (this is just an example):
1730
-
[GSRD User Manual]: https://altera-fpga.github.io/rel-24.2/docs/embedded-designs/agilex-5/e-series/premium/gsrd/ug-gsrd-agx5e-premium/
1731
-
In the above example, user only needs to include [GSRD User Manual] in document for live link to work.-->
0 commit comments