From: Alan Tull <atull@kernel.org>
To: Moritz Fischer <mdf@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Federico Vaga <federico.vaga@cern.ch>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
linux-doc@vger.kernel.org, Alan Tull <atull@kernel.org>
Subject: [PATCH v3 0/4] fpga: add devm managed create APIs
Date: Wed, 26 Sep 2018 11:12:18 -0500 [thread overview]
Message-ID: <1537978342-17697-1-git-send-email-atull@kernel.org> (raw)
Implement managed devm_fpga_(mgr|bridge|region)_create() functions.
Patchset is dependent on the patches that were acked/sent upstream:
https://lkml.org/lkml/2018/9/12/639
v3 changes:
* take out unclear explanation fpga_(mgr|br|region)_unregister
* Add acks
* drop the separately resent "dt-bindings: fpga: fix freeze controller compatible in region doc"
* drop some of the acked patches that I send to Greg
Alan Tull (4):
fpga: mgr: add devm_fpga_mgr_create
fpga: bridge: add devm_fpga_bridge_create
fpga: add devm_fpga_region_create
docs: fpga: document programming fpgas using regions
Documentation/driver-api/fpga/fpga-bridge.rst | 37 ++----
Documentation/driver-api/fpga/fpga-mgr.rst | 126 +++------------------
Documentation/driver-api/fpga/fpga-programming.rst | 107 +++++++++++++++++
Documentation/driver-api/fpga/fpga-region.rst | 91 +++++++--------
Documentation/driver-api/fpga/index.rst | 2 +
Documentation/driver-api/fpga/intro.rst | 2 +-
drivers/fpga/altera-cvp.c | 8 +-
drivers/fpga/altera-fpga2sdram.c | 8 +-
drivers/fpga/altera-freeze-bridge.c | 13 +--
drivers/fpga/altera-hps2fpga.c | 7 +-
drivers/fpga/altera-pr-ip-core.c | 9 +-
drivers/fpga/altera-ps-spi.c | 11 +-
drivers/fpga/dfl-fme-br.c | 11 +-
drivers/fpga/dfl-fme-mgr.c | 11 +-
drivers/fpga/dfl-fme-region.c | 6 +-
drivers/fpga/dfl.c | 6 +-
drivers/fpga/fpga-bridge.c | 68 +++++++++--
drivers/fpga/fpga-mgr.c | 64 +++++++++--
drivers/fpga/fpga-region.c | 65 +++++++++--
drivers/fpga/ice40-spi.c | 10 +-
drivers/fpga/machxo2-spi.c | 11 +-
drivers/fpga/of-fpga-region.c | 6 +-
drivers/fpga/socfpga-a10.c | 5 +-
drivers/fpga/socfpga.c | 10 +-
drivers/fpga/ts73xx-fpga.c | 11 +-
drivers/fpga/xilinx-pr-decoupler.c | 4 +-
drivers/fpga/xilinx-spi.c | 12 +-
drivers/fpga/zynq-fpga.c | 5 +-
include/linux/fpga/fpga-bridge.h | 4 +
include/linux/fpga/fpga-mgr.h | 4 +
include/linux/fpga/fpga-region.h | 4 +
31 files changed, 412 insertions(+), 326 deletions(-)
create mode 100644 Documentation/driver-api/fpga/fpga-programming.rst
--
2.7.4
next reply other threads:[~2018-09-26 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 16:12 Alan Tull [this message]
2018-09-26 16:12 ` [PATCH v3 1/4] fpga: mgr: add devm_fpga_mgr_create Alan Tull
2018-10-15 14:54 ` Alan Tull
2018-10-15 17:32 ` Moritz Fischer
2018-10-16 7:02 ` Federico Vaga
2018-09-26 16:12 ` [PATCH v3 2/4] fpga: bridge: add devm_fpga_bridge_create Alan Tull
2018-09-26 16:12 ` [PATCH v3 3/4] fpga: add devm_fpga_region_create Alan Tull
2018-10-15 20:10 ` Moritz Fischer
2018-09-26 16:12 ` [PATCH v3 4/4] docs: fpga: document programming fpgas using regions Alan Tull
2018-10-15 20:11 ` Moritz Fischer
2018-10-15 20:40 ` Alan Tull
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=1537978342-17697-1-git-send-email-atull@kernel.org \
--to=atull@kernel.org \
--cc=corbet@lwn.net \
--cc=federico.vaga@cern.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=rdunlap@infradead.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).