From: iansdannapel@gmail.com
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-fpga@vger.kernel.org, mdf@kernel.org, yilun.xu@intel.com,
trix@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de, neil.armstrong@linaro.org,
mani@kernel.org, kever.yang@rock-chips.com, dev@kael-k.io,
iansdannapel@gmail.com
Subject: [PATCH v5 0/3] Add Efinix FPGA SPI programming support
Date: Wed, 19 Nov 2025 19:47:03 +0100 [thread overview]
Message-ID: <20251119184708.566461-1-iansdannapel@gmail.com> (raw)
From: Ian Dannapel <iansdannapel@gmail.com>
Hi all,
This is the v5 version of the series that adds support for programming
Efinix FPGAs over SPI using the fpga-mgr subsystem.
The driver implements the passive-serial configuration
protocol and allows loading full bitstreams via an SPI controller. The
binding describes the Efinix Trion SPI interface and documents the DT
requirements for enabling the driver.
All v4 remarks should now be adressed.
Please let me know if further adjustments are needed.
Testing:
- Verified on an Efinix Trion T13 custom board
- Tested full bitstream configuration over SPI at 25 MHz
Changelog since v4:
dt-bindings: fpga: Add Efinix SPI programming bindings:
- efinix,spi.yaml: remove unused binding efinix,fpga-spi
- Rename efinix,spi.yaml to match a compatible (efinix,trion-spi.yaml)
- efinix,trion-spi.yaml: remove notes not relevant to hardware description
fpga-mgr: Add Efinix SPI programming driver
- efinix-spi.c: improve driver description header
- efinix-spi.c: replace hardcoded numbers with macros
- efinix-spi.c: use spi_message_init_with_transfers instead of spi message init + tail
- efinix-spi.c: rework write logic to avoid deasserting the cs or resetting the hardware in between write chunks
Ian Dannapel (3):
dt-bindings: vendor-prefix: Add prefix for Efinix, Inc.
dt-bindings: fpga: Add Efinix SPI programming bindings
fpga-mgr: Add Efinix SPI programming driver
.../bindings/fpga/efinix,trion-spi.yaml | 77 ++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
drivers/fpga/Kconfig | 7 +
drivers/fpga/Makefile | 1 +
drivers/fpga/efinix-spi.c | 256 ++++++++++++++++++
5 files changed, 343 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fpga/efinix,trion-spi.yaml
create mode 100644 drivers/fpga/efinix-spi.c
--
2.43.0
next reply other threads:[~2025-11-19 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 18:47 iansdannapel [this message]
2025-11-19 18:47 ` [PATCH v5 1/3] dt-bindings: vendor-prefix: Add prefix for Efinix, Inc iansdannapel
2025-11-20 14:11 ` Krzysztof Kozlowski
2025-11-19 18:47 ` [PATCH v5 2/3] dt-bindings: fpga: Add Efinix SPI programming bindings iansdannapel
2025-11-19 20:33 ` Rob Herring (Arm)
2025-11-20 14:12 ` Krzysztof Kozlowski
2025-11-20 15:55 ` Ian Dannapel
2025-11-20 16:42 ` Krzysztof Kozlowski
2025-11-19 18:47 ` [PATCH v5 3/3] fpga-mgr: Add Efinix SPI programming driver iansdannapel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251119184708.566461-1-iansdannapel@gmail.com \
--to=iansdannapel@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mdf@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).