Searched refs:FPGA (Results 1 – 25 of 165) sorted by relevance
1234567
/linux-6.12.1/drivers/fpga/ |
D | Kconfig | 3 # FPGA framework configuration 6 menuconfig FPGA config 7 tristate "FPGA Configuration Framework" 10 kernel. The FPGA framework adds an FPGA manager class and FPGA 13 if FPGA 16 tristate "Altera SOCFPGA FPGA Manager" 19 FPGA manager driver support for Altera SOCFPGA. 26 FPGA manager driver support for Altera Arria10 SoCFPGA. 41 tristate "Altera FPGA Passive Serial over SPI" 45 FPGA manager driver support for Altera Arria/Cyclone/Stratix [all …]
|
/linux-6.12.1/Documentation/driver-api/fpga/ |
D | intro.rst | 4 The FPGA subsystem supports reprogramming FPGAs dynamically under 5 Linux. Some of the core intentions of the FPGA subsystems are: 7 * The FPGA subsystem is vendor agnostic. 9 * The FPGA subsystem separates upper layers (userspace interfaces and 11 FPGA. 23 FPGA Manager 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 32 FPGA Bridge 35 FPGA Bridges prevent spurious signals from going out of an FPGA or a [all …]
|
D | fpga-programming.rst | 1 In-kernel API for FPGA Programming 7 The in-kernel API for FPGA programming is a combination of APIs from 8 FPGA manager, bridge, and regions. The actual function used to 9 trigger FPGA programming is fpga_region_program_fpga(). 12 the FPGA manager and bridges. It will: 15 * lock the mutex of the region's FPGA manager 16 * build a list of FPGA bridges if a method has been specified to do so 18 * program the FPGA using info passed in :c:expr:`fpga_region->info`. 22 The struct fpga_image_info specifies what FPGA image to program. It is 26 How to program an FPGA using a region [all …]
|
D | fpga-region.rst | 1 FPGA Region 7 This document is meant to be a brief overview of the FPGA region API usage. A 12 an FPGA Manager and a bridge (or bridges) with a reprogrammable region of an 13 FPGA or the whole FPGA. The API provides a way to register a region and to 18 to program the FPGA and then DT to handle enumeration. The common region code 24 * which FPGA manager to use to do the programming 28 Additional info needed to program the FPGA image is passed in the struct 37 How to add a new FPGA region 45 API to add a new FPGA region 48 * struct fpga_region - The FPGA region struct [all …]
|
D | fpga-mgr.rst | 1 FPGA Manager 7 The FPGA manager core exports a set of functions for programming an FPGA with 10 The FPGA image data itself is very manufacturer specific, but for our purposes 11 it's just binary data. The FPGA manager core won't parse it. 13 The FPGA image to be programmed can be in a scatter gather list, a single 20 FPGA image as well as image-specific particulars such as whether the image was 23 How to support a new FPGA device 26 To add another FPGA manager, write a driver that implements a set of ops. The 53 mgr = fpga_mgr_register(dev, "Altera SOCFPGA FPGA Manager", 80 do the programming sequence for this particular FPGA. These ops return 0 for [all …]
|
D | fpga-bridge.rst | 1 FPGA Bridge 4 API to implement a new FPGA bridge 7 * struct fpga_bridge - The FPGA Bridge structure 13 the module that registers the FPGA bridge as the owner.
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-class-fpga-manager | 13 wrong during FPGA programming (something that the driver can't 18 This is a superset of FPGA states and fpga manager driver 20 to get the FPGA into a known operating state. It's a sequence, 21 though some steps may get skipped. Valid FPGA states will vary 25 * power off = FPGA power is off 26 * power up = FPGA reports power is up 27 * reset = FPGA held in reset state 30 * write init = preparing FPGA for programming 31 * write init error = Error while preparing FPGA for programming 32 * write = FPGA ready to receive image data [all …]
|
D | sysfs-bus-mcb | 11 Description: The FPGA's revision number 17 Description: The FPGA's minor number 23 Description: The FPGA's model number 29 Description: The FPGA's name
|
D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility 6 of the FPGA reconfiguration hardware and image. This value 8 FPGA region. This interface returns the compat_id value or
|
D | sysfs-class-ocxl | 44 Control whether the FPGA is reloaded on a link reset. Enabled 45 through a vendor-specific logic block on the FPGA. 48 0 Do not reload FPGA image from flash 49 1 Reload FPGA image from flash
|
D | sysfs-platform-dfl-fme | 5 Description: Read-only. One DFL FPGA device may have more than 1 7 number of ports on the FPGA device when read it. 13 Description: Read-only. It returns Bitstream (static FPGA region) 15 and other information of this static FPGA region. 21 Description: Read-only. It returns Bitstream (static FPGA region) meta 23 information of this static FPGA region. 29 Description: Read-only. It returns cache size of this FPGA device. 35 Description: Read-only. It returns fabric version of this FPGA device. 44 this FPGA belongs to, only valid for integrated solution. 126 Description: Read-Only. It returns FPGA device temperature in millidegrees [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/bus/ |
D | ts-nbus.txt | 4 Systems FPGA on the TS-4600 SoM. 10 - pwms : The PWM bound to the FPGA 11 - ts,data-gpios : The 8 GPIO pins connected to the data lines on the FPGA 12 - ts,csn-gpios : The GPIO pin connected to the csn line on the FPGA 13 - ts,txrx-gpios : The GPIO pin connected to the txrx line on the FPGA 14 - ts,strobe-gpios : The GPIO pin connected to the stobe line on the FPGA 15 - ts,ale-gpios : The GPIO pin connected to the ale line on the FPGA 16 - ts,rdy-gpios : The GPIO pin connected to the rdy line on the FPGA
|
/linux-6.12.1/Documentation/driver-api/ |
D | xillybus.rst | 2 Xillybus driver for generic FPGA interface 22 -- Host never reads from the FPGA 37 An FPGA (Field Programmable Gate Array) is a piece of logic hardware, which 48 level, even lower than assembly language. In order to allow FPGA designers to 51 FPGA parallels of library functions. IP cores may implement certain 57 One of the daunting tasks in FPGA design is communicating with a fullblown 60 (registers, interrupts, DMA etc.) is a project in itself. When the FPGA's 62 make sense to design the FPGA's interface logic specifically for the project. 63 A special driver is then written to present the FPGA as a well-known interface 65 FPGA differently than any device on the bus. [all …]
|
/linux-6.12.1/Documentation/fpga/ |
D | dfl.rst | 2 FPGA Device Feature List (DFL) Framework Overview 12 The Device Feature List (DFL) FPGA framework (and drivers according to 15 configure, enumerate, open and access FPGA accelerators on platforms which 17 enables system level management functions such as FPGA reconfiguration. 24 walk through these predefined data structures to enumerate FPGA features: 25 FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features, 56 FPGA Interface Unit (FIU) represents a standalone functional unit for the 57 interface to FPGA, e.g. the FPGA Management Engine (FME) and Port (more 60 Accelerated Function Unit (AFU) represents an FPGA programmable region and 75 and can be implemented in register regions of any FPGA device. [all …]
|
/linux-6.12.1/drivers/char/xillybus/ |
D | Kconfig | 10 tristate "Xillybus generic FPGA interface" 16 programmable logic (FPGA). The driver probes the hardware for 28 with the FPGA. The module will be called xillybus_pcie. 43 tristate "XillyUSB: Xillybus generic FPGA interface for USB" 49 with the FPGA. 52 the FPGA. The module will be called xillyusb.
|
/linux-6.12.1/Documentation/devicetree/bindings/fpga/ |
D | altera-socfpga-fpga-mgr.txt | 1 Altera SOCFPGA FPGA Manager 6 - The first index is for FPGA manager register access. 7 - The second index is for writing FPGA configuration data. 8 - interrupts : interrupt for the FPGA Manager device.
|
D | lattice-machxo2-spi.txt | 1 Lattice MachXO2 Slave SPI FPGA Manager 10 - reg: spi chip select of the FPGA 12 Example for full FPGA configuration:
|
D | altera-socfpga-a10-fpga-mgr.txt | 1 Altera SOCFPGA Arria10 FPGA Manager 6 - The first index is for FPGA manager register access. 7 - The second index is for writing FPGA configuration data.
|
/linux-6.12.1/Documentation/devicetree/bindings/gpio/ |
D | gpio-ts4900.txt | 1 * Technologic Systems I2C-FPGA's GPIO controller bindings 3 This bindings describes the GPIO controller for Technologic's FPGA core. 4 TS-4900's FPGA encodes the GPIO state on 3 bits, whereas the TS-7970's FPGA
|
/linux-6.12.1/drivers/misc/altera-stapl/ |
D | Kconfig | 2 comment "Altera FPGA firmware download module (requires I2C)" 6 tristate "Altera FPGA firmware download module" 9 An Altera FPGA module. Say Y when you want to support this tool.
|
/linux-6.12.1/Documentation/devicetree/bindings/interrupt-controller/ |
D | arm,versatile-fpga-irq.txt | 1 * ARM Versatile FPGA interrupt controller 3 One or more FPGA IRQ controllers can be synthesized in an ARM reference board 12 as the FPGA IRQ controller has no configuration options for interrupt 14 - reg: The register bank for the FPGA interrupt controller. 36 - interrupts: if the FPGA IRQ controller is cascaded, i.e. if its IRQ
|
/linux-6.12.1/drivers/fpga/tests/ |
D | Kconfig | 2 tristate "KUnit test for the FPGA subsystem" if !KUNIT_ALL_TESTS 3 depends on FPGA && FPGA_REGION && FPGA_BRIDGE && KUNIT=y 6 This builds unit tests for the FPGA subsystem
|
/linux-6.12.1/drivers/misc/keba/ |
D | Kconfig | 3 tristate "KEBA CP500 system FPGA support" 7 This driver supports the KEBA CP500 system FPGA, which is used in 9 system FPGA as separate devices. A driver is needed for each sub
|
/linux-6.12.1/Documentation/translations/zh_CN/arch/openrisc/ |
D | openrisc_port.rst | 52 3) 在FPGA上运行(可选) 54 OpenRISC社区通常使用FuseSoC来管理构建和编程SoC到FPGA中。 下面是用 56 FPGA RTL是从FuseSoC IP核库中下载的代码,并使用FPGA供应商工具构建。
|
/linux-6.12.1/Documentation/translations/zh_TW/arch/openrisc/ |
D | openrisc_port.rst | 52 3) 在FPGA上運行(可選) 54 OpenRISC社區通常使用FuseSoC來管理構建和編程SoC到FPGA中。 下面是用 56 FPGA RTL是從FuseSoC IP核庫中下載的代碼,並使用FPGA供應商工具構建。
|
1234567