From: Rob Herring <robh@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: devicetree@vger.kernel.org, git@xilinx.com, trix@redhat.com,
linux-fpga@vger.kernel.org, michal.simek@xilinx.com,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
mdf@kernel.org, linux-arm-kernel@lists.infradead.org,
christian.koenig@amd.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] fpga: region: Add fpga-region property 'fpga-config-from-dmabuf'
Date: Fri, 9 Apr 2021 09:47:27 -0500 [thread overview]
Message-ID: <20210409144727.GA3625530@robh.at.kernel.org> (raw)
In-Reply-To: <20210402090933.32276-2-nava.manne@xilinx.com>
On Fri, Apr 02, 2021 at 02:39:31PM +0530, Nava kishore Manne wrote:
> Add "fpga-config-from-dmabuf" property to allow the bitstream
> configuration from pre-allocated dma-buffer.
>
> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> ---
> Documentation/devicetree/bindings/fpga/fpga-region.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/fpga/fpga-region.txt b/Documentation/devicetree/bindings/fpga/fpga-region.txt
> index 969ca53bb65e..c573cf258d60 100644
> --- a/Documentation/devicetree/bindings/fpga/fpga-region.txt
> +++ b/Documentation/devicetree/bindings/fpga/fpga-region.txt
> @@ -177,6 +177,8 @@ Optional properties:
> it indicates that the FPGA has already been programmed with this image.
> If this property is in an overlay targeting a FPGA region, it is a
> request to program the FPGA with that image.
> +- fpga-config-from-dmabuf : boolean, set if the FPGA configured done from the
> + pre-allocated dma-buffer.
Sounds like an implementation detail of the OS. Doesn't belong in DT.
Rob
> - fpga-bridges : should contain a list of phandles to FPGA Bridges that must be
> controlled during FPGA programming along with the parent FPGA bridge.
> This property is optional if the FPGA Manager handles the bridges.
> --
> 2.18.0
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-09 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:09 [PATCH RFC 0/3] Adds support to allow the bitstream configuration from pre-allocated dma-buffer Nava kishore Manne
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 [this message]
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=20210409144727.GA3625530@robh.at.kernel.org \
--to=robh@kernel.org \
--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=nava.manne@xilinx.com \
--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).