From: Nava kishore Manne <nava.manne@xilinx.com>
To: <atull@kernel.org>, <mdf@kernel.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <michal.simek@xilinx.com>,
<rajanv@xilinx.com>, <jollys@xilinx.com>, <nava.manne@xilinx.com>,
<linux-fpga@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <chinnikishore369@gmail.com>
Subject: [PATCH v4 0/3] Add Bitstream configuration support for ZynqMP
Date: Tue, 2 Apr 2019 18:01:20 +0530 [thread overview]
Message-ID: <20190402123123.915-1-nava.manne@xilinx.com> (raw)
Nava kishore Manne (3):
firmware: xilinx: Add fpga API's
dt-bindings: fpga: Add bindings for ZynqMP fpga driver
fpga manager: Adding FPGA Manager support for Xilinx zynqmp
.../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 25 +++
drivers/firmware/xilinx/zynqmp.c | 46 +++++
drivers/fpga/Kconfig | 9 +
drivers/fpga/Makefile | 1 +
drivers/fpga/zynqmp-fpga.c | 159 ++++++++++++++++++
include/linux/firmware/xlnx-zynqmp.h | 10 ++
6 files changed, 250 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.txt
create mode 100644 drivers/fpga/zynqmp-fpga.c
--
2.18.0
next reply other threads:[~2019-04-02 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 12:31 Nava kishore Manne [this message]
2019-04-02 12:31 ` [PATCH v4 1/3] firmware: xilinx: Add fpga API's Nava kishore Manne
2019-04-08 17:14 ` Moritz Fischer
2019-04-09 6:33 ` Michal Simek
2019-04-09 8:54 ` Nava kishore Manne
2019-04-09 15:54 ` Moritz Fischer
2019-04-02 12:31 ` [PATCH v4 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne
2019-04-02 12:31 ` [PATCH v4 3/3] fpga manager: Adding FPGA Manager support for Xilinx zynqmp Nava kishore Manne
2019-04-02 13:31 ` Moritz Fischer
2019-04-02 18:27 ` Alan Tull
2019-04-08 12:39 ` Nava kishore Manne
2019-04-08 14:17 ` Alan Tull
2019-04-08 14:36 ` Michal Simek
2019-04-08 16:51 ` Moritz Fischer
2019-04-08 20:27 ` Alan Tull
2019-04-09 6:34 ` Michal Simek
2019-04-09 6:50 ` Nava kishore Manne
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=20190402123123.915-1-nava.manne@xilinx.com \
--to=nava.manne@xilinx.com \
--cc=atull@kernel.org \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jollys@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rajanv@xilinx.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
all inboxes | Powered by JetHome®