~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/fpga/intro.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 Introduction
  2 ============
  3 
  4 The FPGA subsystem supports reprogramming FPGAs dynamically under
  5 Linux.  Some of the core intentions of the FPGA subsystems are:
  6 
  7 * The FPGA subsystem is vendor agnostic.
  8 
  9 * The FPGA subsystem separates upper layers (userspace interfaces and
 10   enumeration) from lower layers that know how to program a specific
 11   FPGA.
 12 
 13 * Code should not be shared between upper and lower layers.  This
 14   should go without saying.  If that seems necessary, there's probably
 15   framework functionality that can be added that will benefit
 16   other users.  Write the linux-fpga mailing list and maintainers and
 17   seek out a solution that expands the framework for broad reuse.
 18 
 19 * Generally, when adding code, think of the future.  Plan for reuse.
 20 
 21 The framework in the kernel is divided into:
 22 
 23 FPGA Manager
 24 ------------
 25 
 26 If you are adding a new FPGA or a new method of programming an FPGA,
 27 this is the subsystem for you.  Low level FPGA manager drivers contain
 28 the knowledge of how to program a specific device.  This subsystem
 29 includes the framework in fpga-mgr.c and the low level drivers that
 30 are registered with it.
 31 
 32 FPGA Bridge
 33 -----------
 34 
 35 FPGA Bridges prevent spurious signals from going out of an FPGA or a
 36 region of an FPGA during programming.  They are disabled before
 37 programming begins and re-enabled afterwards.  An FPGA bridge may be
 38 actual hard hardware that gates a bus to a CPU or a soft ("freeze")
 39 bridge in FPGA fabric that surrounds a partial reconfiguration region
 40 of an FPGA.  This subsystem includes fpga-bridge.c and the low level
 41 drivers that are registered with it.
 42 
 43 FPGA Region
 44 -----------
 45 
 46 If you are adding a new interface to the FPGA framework, add it on top
 47 of an FPGA region.
 48 
 49 The FPGA Region framework (fpga-region.c) associates managers and
 50 bridges as reconfigurable regions.  A region may refer to the whole
 51 FPGA in full reconfiguration or to a partial reconfiguration region.
 52 
 53 The Device Tree FPGA Region support (of-fpga-region.c) handles
 54 reprogramming FPGAs when device tree overlays are applied.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php