From: iansdannapel@gmail.com
To: linux-fpga@vger.kernel.org
Cc: "Moritz Fischer" <mdf@kernel.org>, "Wu Hao" <hao.wu@intel.com>,
"Xu Yilun" <yilun.xu@intel.com>, "Tom Rix" <trix@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Aradhya Bhatia" <a-bhatia1@ti.com>,
"Ian Dannapel" <iansdannapel@gmail.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Subject: [v4 0/3] Add Efinix FPGA SPI programming support
Date: Fri, 28 Feb 2025 10:47:29 +0100 [thread overview]
Message-ID: <20250228094732.54642-1-iansdannapel@gmail.com> (raw)
From: Ian Dannapel <iansdannapel@gmail.com>
This patch series introduces support for Efinix FPGA devices
through SPI-based programming.
Currently, only Trion devices are tested. Topaz and Titanium series are
theoretically supported because of the similarity with Trion, but the
driver is only documentation based.
Changes since v3:
- major rework on the driver spi write approach
- indirect CS assert using spi_transfer instead of duplicating the
SPI controller property
- locked SPI bus transfer to avoid possible conflicts with other
devices on the bus
- file name and compatible strings renamed to better match device
- minor improvements/fixes
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
.../devicetree/bindings/fpga/efinix,spi.yaml | 81 +++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
drivers/fpga/Kconfig | 7 +
drivers/fpga/Makefile | 1 +
drivers/fpga/efinix-spi.c | 212 ++++++++++++++++++
5 files changed, 303 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fpga/efinix,spi.yaml
create mode 100644 drivers/fpga/efinix-spi.c
--
2.43.0
next reply other threads:[~2025-02-28 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:47 iansdannapel [this message]
2025-02-28 9:47 ` [v4 1/3] dt-bindings: vendor-prefix: Add prefix for Efinix, Inc iansdannapel
2025-02-28 18:29 ` Conor Dooley
2025-03-01 13:10 ` Krzysztof Kozlowski
2025-03-04 11:24 ` Alexander Dahl
2025-02-28 9:47 ` [v4 2/3] dt-bindings: fpga: Add Efinix SPI programming bindings iansdannapel
2025-02-28 18:28 ` Conor Dooley
2025-03-03 10:10 ` Ian Dannapel
2025-03-03 10:29 ` Ian Dannapel
2025-03-03 10:33 ` Krzysztof Kozlowski
2025-03-03 10:31 ` Conor Dooley
2025-03-03 10:34 ` Krzysztof Kozlowski
2025-03-01 13:13 ` Krzysztof Kozlowski
2025-02-28 9:47 ` [v4 3/3] fpga-mgr: Add Efinix SPI programming driver iansdannapel
2025-03-03 11:57 ` Manne, Nava kishore
2025-03-03 12:16 ` Ian Dannapel
2025-03-16 15:03 ` Xu Yilun
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=20250228094732.54642-1-iansdannapel@gmail.com \
--to=iansdannapel@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a-bhatia1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rafal@milecki.pl \
--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).