From: Nava kishore Manne <nava.manne@xilinx.com>
To: <mdf@kernel.org>, <trix@redhat.com>, <robh+dt@kernel.org>,
<michal.simek@xilinx.com>, <sumit.semwal@linaro.org>,
<christian.koenig@amd.com>, <linux-fpga@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <git@xilinx.com>
Cc: Nava kishore Manne <nava.manne@xilinx.com>
Subject: [PATCH RFC 0/3] Adds support to allow the bitstream configuration from pre-allocated dma-buffer
Date: Fri, 2 Apr 2021 14:39:30 +0530 [thread overview]
Message-ID: <20210402090933.32276-1-nava.manne@xilinx.com> (raw)
Nava kishore Manne (3):
fpga: region: Add fpga-region property 'fpga-config-from-dmabuf'
fpga: support loading from a pre-allocated buffer
fpga: zynqmp: Use the scatterlist interface
.../devicetree/bindings/fpga/fpga-region.txt | 2 +
drivers/fpga/fpga-mgr.c | 126 +++++++++++++++++-
drivers/fpga/of-fpga-region.c | 3 +
drivers/fpga/zynqmp-fpga.c | 35 +++++
include/linux/fpga/fpga-mgr.h | 6 +-
5 files changed, 169 insertions(+), 3 deletions(-)
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-04-02 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:09 Nava kishore Manne [this message]
2021-04-02 9:09 ` [PATCH RFC 1/3] fpga: region: Add fpga-region property 'fpga-config-from-dmabuf' Nava kishore Manne
2021-04-09 14:47 ` Rob Herring
2021-04-02 9:09 ` [PATCH RFC 2/3] fpga: support loading from a pre-allocated buffer Nava kishore Manne
2021-04-06 6:42 ` Martin Hundebøll
2021-04-02 9:09 ` [PATCH RFC 3/3] fpga: zynqmp: Use the scatterlist interface Nava kishore Manne
2021-04-02 14:35 ` [PATCH RFC 0/3] Adds support to allow the bitstream configuration from pre-allocated dma-buffer Tom Rix
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=20210402090933.32276-1-nava.manne@xilinx.com \
--to=nava.manne@xilinx.com \
--cc=christian.koenig@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=git@xilinx.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=trix@redhat.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).