From: <atull@opensource.altera.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
Josh Cartwright <joshc@ni.com>,
gregkh@linuxfoundation.org, monstr@monstr.eu,
michal.simek@xilinx.com, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, pantelis.antoniou@konsulko.com,
delicious.quinoa@gmail.com, dinguyen@opensource.altera.com,
Alan Tull <atull@opensource.altera.com>
Subject: [PATCH v13 0/6] simple fpga bus and fpga bridge framework
Date: Tue, 3 Nov 2015 11:10:58 -0600 [thread overview]
Message-ID: <1446570664-10293-1-git-send-email-atull@opensource.altera.com> (raw)
From: Alan Tull <atull@opensource.altera.com>
These patches are too late for this merge window; I'm submitting
them for those who are reviewing, especially the bindings.
Changes since v12:
Change DT property from "init-val" to "bridge-enable"
Use proposed DT common property "firmware-name" instead of "fpga-firmware"
Clean up cruft from simple-fpga-bus DT bindings example
Support Simple FPGA Bus when FPGA Bridges are compiled out.
Cleanup and nits
The Simple FPGA Bus provides a manufacturer-agnostic interface for
reprogramming FPGAs using Device Tree Overlays. It uses the FPGA Bridge
Framework and the upstreamed FPGA Manager Framework. In the case where
FPGA Bridges are not needed, they don't need to be specified in the DT
and can compiled out, if desired.
Alan Tull (6):
fpga: add usage documentation for simple fpga bus
fpga: add bindings document for simple fpga bus
fpga: add simple-fpga-bus
fpga: add fpga bridge framework
ARM: socfpga: add bindings document for fpga bridge drivers
ARM: socfpga: fpga bridge driver support
.../bindings/fpga/altera-fpga2sdram-bridge.txt | 15 +
.../bindings/fpga/altera-hps2fpga-bridge.txt | 31 ++
.../devicetree/bindings/fpga/simple-fpga-bus.txt | 74 +++++
Documentation/fpga/simple-fpga-bus.txt | 58 ++++
drivers/fpga/Kconfig | 21 ++
drivers/fpga/Makefile | 7 +
drivers/fpga/altera-fpga2sdram.c | 185 ++++++++++++
drivers/fpga/altera-hps2fpga.c | 233 +++++++++++++++
drivers/fpga/fpga-bridge.c | 229 +++++++++++++++
drivers/fpga/simple-fpga-bus.c | 323 +++++++++++++++++++++
include/linux/fpga/fpga-bridge.h | 74 +++++
11 files changed, 1250 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt
create mode 100644 Documentation/devicetree/bindings/fpga/altera-hps2fpga-bridge.txt
create mode 100644 Documentation/devicetree/bindings/fpga/simple-fpga-bus.txt
create mode 100644 Documentation/fpga/simple-fpga-bus.txt
create mode 100644 drivers/fpga/altera-fpga2sdram.c
create mode 100644 drivers/fpga/altera-hps2fpga.c
create mode 100644 drivers/fpga/fpga-bridge.c
create mode 100644 drivers/fpga/simple-fpga-bus.c
create mode 100644 include/linux/fpga/fpga-bridge.h
--
1.9.1
next reply other threads:[~2015-11-03 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 17:10 atull [this message]
2015-11-03 17:10 ` [PATCH v13 1/6] fpga: add usage documentation for simple fpga bus atull
2015-11-03 17:11 ` [PATCH v13 2/6] fpga: add bindings document " atull
[not found] ` <1446570664-10293-1-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2015-11-03 17:11 ` [PATCH v13 3/6] fpga: add simple-fpga-bus atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2015-11-03 17:11 ` [PATCH v13 4/6] fpga: add fpga bridge framework atull
2015-11-19 4:50 ` Moritz Fischer
2015-11-20 15:08 ` atull
2015-11-03 17:11 ` [PATCH v13 5/6] ARM: socfpga: add bindings document for fpga bridge drivers atull
2015-11-03 17:11 ` [PATCH v13 6/6] ARM: socfpga: fpga bridge driver support atull
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=1446570664-10293-1-git-send-email-atull@opensource.altera.com \
--to=atull@opensource.altera.com \
--cc=corbet@lwn.net \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joshc@ni.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=moritz.fischer@ettus.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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).