From: <atull@opensource.altera.com>
To: Rob Herring <robh+dt@kernel.org>, pantelis.antoniou@konsulko.com
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, delicious.quinoa@gmail.com,
dinguyen@opensource.altera.com,
Alan Tull <atull@opensource.altera.com>
Subject: [PATCH v16 0/6] Device Tree support for FPGA programming
Date: Fri, 5 Feb 2016 15:29:57 -0600 [thread overview]
Message-ID: <1454707803-27947-1-git-send-email-atull@opensource.altera.com> (raw)
From: Alan Tull <atull@opensource.altera.com>
v16 Refactors the FPGA Area and FPGA Bus into single thing called an
FPGA Region and eliminates using simple-bus. I'm using the word
"region" as it's a term is used in the literature of both the major
FPGA manufacturors.
Changes for v16:
* Refactor the FPGA Area and FPGA Bus into a FPGA Region.
* Don't use simple-bus.
* FPGA Managers and FPGA Bridges are now specified by phandle using the
"fpga-mgr" and "fpga-bridges" properties. fpga-bridges can specify
more than one bridge.
* Device Tree overlays should be targeted to a FPGA Region.
* The overlays need only contain firmware-name and the child nodes.
* To model a system containing >1 partial reconfiguration region,
an overlay could add FPGA Regions to the base FPGA Regions.
* Child FPGA Regions inherit the parent FGPA Manager, but specify
their own set of bridges if needes as partial reconfig regions
will likely need their own bridges.
* All this is discussed in bindings/fpga/fpga-region.txt
One other highlight:
The little engine that runs this thing is a reconfig notifier
in fpga-region.c. This notifier that will program an FPGA if a
"firmware-name" property gets added to a fpga-region. Then
it will call of_platform_populate(). The current behavior in Linux
when a DT overlay is applied is that the reconfig notifications
go out in heirarchical order: first notifications are for the
properties, then notifications for the child nodes. So an overlay
that adds a 'firmware-name' property and some child nodes to a
fpga-region will cause FPGA programming and child node
populating in the right order.
One issue with the dynamic DT stuff:
I've tried returning and error from the notifier if FPGA programming
fails; the error is noted on the console, but the child nodes
get probed anyway.
Alan Tull (6):
fpga: add bindings document for fpga region
add sysfs document for fpga bridge class
ARM: socfpga: add bindings document for fpga bridge drivers
fpga: add fpga bridge framework
fpga: fpga-region: device tree control for FPGA
ARM: socfpga: fpga bridge driver support
Documentation/ABI/testing/sysfs-class-fpga-bridge | 11 +
.../bindings/fpga/altera-fpga2sdram-bridge.txt | 15 +
.../bindings/fpga/altera-hps2fpga-bridge.txt | 47 ++
.../devicetree/bindings/fpga/fpga-region.txt | 348 +++++++++++++++
drivers/fpga/Kconfig | 21 +
drivers/fpga/Makefile | 7 +
drivers/fpga/altera-fpga2sdram.c | 174 ++++++++
drivers/fpga/altera-hps2fpga.c | 213 +++++++++
drivers/fpga/fpga-bridge.c | 388 +++++++++++++++++
drivers/fpga/fpga-region.c | 460 ++++++++++++++++++++
include/linux/fpga/fpga-bridge.h | 55 +++
11 files changed, 1739 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-bridge
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/fpga-region.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/fpga-region.c
create mode 100644 include/linux/fpga/fpga-bridge.h
--
1.7.9.5
next reply other threads:[~2016-02-05 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 21:29 atull [this message]
2016-02-05 21:29 ` [PATCH v16 1/6] fpga: add bindings document for fpga region atull
2016-02-05 22:44 ` Josh Cartwright
2016-02-07 1:16 ` atull
2016-02-22 2:54 ` Rob Herring
2016-02-05 21:29 ` [PATCH v16 2/6] add sysfs document for fpga bridge class atull
2016-02-05 21:30 ` [PATCH v16 3/6] ARM: socfpga: add bindings document for fpga bridge drivers atull
2016-02-05 21:30 ` [PATCH v16 4/6] fpga: add fpga bridge framework atull
2016-02-05 21:30 ` [PATCH v16 5/6] fpga: fpga-region: device tree control for FPGA atull
2016-02-05 21:30 ` [PATCH v16 6/6] ARM: socfpga: fpga bridge driver support atull
[not found] ` <1454707803-27947-7-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2016-06-10 2:18 ` Trent Piepho
2016-06-13 19:35 ` atull
2016-06-14 21:00 ` Trent Piepho
2016-07-28 10:28 ` Andrea Galbusera
2016-07-28 15:21 ` atull
2016-07-28 20:26 ` Trent Piepho
[not found] ` <1469737696.30803.152.camel-dVGoCQn2UwS33l2LyG1otL1RWLrjA2wiZkel5v8DVj8@public.gmane.org>
2016-08-01 14:07 ` atull
2016-02-11 20:49 ` [PATCH v16 0/6] Device Tree support for FPGA programming atull
2016-02-11 21:22 ` Rob Herring
2016-02-11 22:08 ` atull
2016-02-11 22:17 ` atull
2016-02-15 17:40 ` Moritz Fischer
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=1454707803-27947-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).