From: Randy Dunlap <rdunlap@infradead.org>
To: Nava kishore Manne <nava.manne@xilinx.com>,
mdf@kernel.org, trix@redhat.com, robh+dt@kernel.org,
michal.simek@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
Cc: git@xilinx.com,
Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Subject: Re: [PATCH v2 3/3] fpga: versal-fpga: Add versal fpga manager driver
Date: Wed, 10 Feb 2021 22:23:44 -0800 [thread overview]
Message-ID: <7016de66-f254-2bd6-ce29-3b44133feaa0@infradead.org> (raw)
In-Reply-To: <20210211060532.23662-4-nava.manne@xilinx.com>
Hi--
On 2/10/21 10:05 PM, Nava kishore Manne wrote:
> diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
> index bf85b9a65ec2..dcd2ed5a7956 100644
> --- a/drivers/fpga/Kconfig
> +++ b/drivers/fpga/Kconfig
> @@ -223,4 +223,12 @@ config FPGA_MGR_ZYNQMP_FPGA
> to configure the programmable logic(PL) through PS
> on ZynqMP SoC.
>
> +config FPGA_MGR_VERSAL_FPGA
> + tristate "Xilinx Versal FPGA"
> + depends on ARCH_ZYNQMP || COMPILE_TEST
> + help
> + Select this option to enable FPGA manager driver support for
> + Xilinx Versal SOC. This driver uses the versal soc firmware
How about consistently capitalizing Versal and SOC (above and below)?
> + interface to load programmable logic(PL) images
> + on versal soc.
> endif # FPGA
thanks.
--
~Randy
prev parent reply other threads:[~2021-02-11 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 6:05 [PATCH v2 0/3] Add Bitstream configuration support for Versal Nava kishore Manne
2021-02-11 6:05 ` [PATCH v2 1/3] drivers: firmware: Add PDI load API support Nava kishore Manne
2021-02-11 6:05 ` [PATCH v2 2/3] dt-bindings: fpga: Add binding doc for versal fpga manager Nava kishore Manne
2021-02-11 14:56 ` Rob Herring
2021-02-12 6:13 ` Nava kishore Manne
2021-02-17 21:06 ` Rob Herring
2021-02-11 6:05 ` [PATCH v2 3/3] fpga: versal-fpga: Add versal fpga manager driver Nava kishore Manne
2021-02-11 6:23 ` Randy Dunlap [this message]
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=7016de66-f254-2bd6-ce29-3b44133feaa0@infradead.org \
--to=rdunlap@infradead.org \
--cc=appana.durga.rao@xilinx.com \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=robh+dt@kernel.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).