From: Greg KH <gregkh@linuxfoundation.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: robh+dt@kernel.org, michal.simek@xilinx.com, mdf@kernel.org,
trix@redhat.com, arnd@arndb.de, rajan.vaja@xilinx.com,
amit.sunil.dhamne@xilinx.com, tejas.patel@xilinx.com,
zou_wei@huawei.com, lakshmi.sai.krishna.potthuri@xilinx.com,
ravi.patel@xilinx.com, iwamatsu@nigauri.org,
wendy.liang@xilinx.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
git@xilinx.com, chinnikishore369@gmail.com
Subject: Re: [RFC v2 2/4] fpga: Add new property to support user-key encrypted bitstream loading
Date: Wed, 9 Jun 2021 11:56:13 +0200 [thread overview]
Message-ID: <YMCQPeGE2gR6QD85@kroah.com> (raw)
In-Reply-To: <20210609055232.4501-3-nava.manne@xilinx.com>
On Wed, Jun 09, 2021 at 11:22:30AM +0530, Nava kishore Manne wrote:
> This patch Adds ‘encrypted-key-name’ property to
> support user-key encrypted bitstream loading
> use case.
>
> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> ---
> Changes for v2:
> -Both DT properties ie; encrypted-key-name and encrypted-user-key-fpga-config
> are targeted to use for the same use cases but ideally encrypted-key-name
> is enough to serve the purpose so updated the file to remove the unwanted
> encrypted-user-key-fpga-config property as suggested by Rob.
>
> Documentation/devicetree/bindings/fpga/fpga-region.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/fpga/fpga-region.txt b/Documentation/devicetree/bindings/fpga/fpga-region.txt
> index d787d57491a1..0de4a1c54650 100644
> --- a/Documentation/devicetree/bindings/fpga/fpga-region.txt
> +++ b/Documentation/devicetree/bindings/fpga/fpga-region.txt
> @@ -177,6 +177,9 @@ 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.
> +- encrypted-key-name : should contain the name of an encrypted key file located
> + on the firmware search path. It will be used to decrypt the FPGA image
> + file with user-key.
What is the format this "user-key" is in? Where is the documentation
for how to use this type of thing?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-09 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 5:52 [RFC v2 0/4]Fpga: adds support to load the user-key encrypted FPGA Image loading Nava kishore Manne
2021-06-09 5:52 ` [RFC v2 1/4] drivers: firmware: Add user encrypted key load API support Nava kishore Manne
2021-06-09 9:55 ` Greg KH
2021-07-09 8:41 ` Nava kishore Manne
2021-07-09 9:49 ` Greg KH
2021-06-09 5:52 ` [RFC v2 2/4] fpga: Add new property to support user-key encrypted bitstream loading Nava kishore Manne
2021-06-09 9:56 ` Greg KH [this message]
2021-07-09 8:48 ` Nava kishore Manne
2021-06-09 5:52 ` [RFC v2 3/4] drivers: fpga: Add user-key encrypted FPGA Image loading support Nava kishore Manne
2021-06-09 5:52 ` [RFC v2 4/4] fpga: zynqmp: " Nava kishore Manne
2021-06-09 9:55 ` [RFC v2 0/4]Fpga: adds support to load the user-key encrypted FPGA Image loading Greg KH
2021-07-09 8:33 ` 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=YMCQPeGE2gR6QD85@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.sunil.dhamne@xilinx.com \
--cc=arnd@arndb.de \
--cc=chinnikishore369@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=iwamatsu@nigauri.org \
--cc=lakshmi.sai.krishna.potthuri@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=rajan.vaja@xilinx.com \
--cc=ravi.patel@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=tejas.patel@xilinx.com \
--cc=trix@redhat.com \
--cc=wendy.liang@xilinx.com \
--cc=zou_wei@huawei.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).