[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210609055232.4501-3-nava.manne@xilinx.com>
Date: Wed, 9 Jun 2021 11:22:30 +0530
From: Nava kishore Manne <nava.manne@...inx.com>
To: <robh+dt@...nel.org>, <michal.simek@...inx.com>, <mdf@...nel.org>,
<trix@...hat.com>, <nava.manne@...inx.com>, <arnd@...db.de>,
<rajan.vaja@...inx.com>, <gregkh@...uxfoundation.org>,
<amit.sunil.dhamne@...inx.com>, <tejas.patel@...inx.com>,
<zou_wei@...wei.com>, <lakshmi.sai.krishna.potthuri@...inx.com>,
<ravi.patel@...inx.com>, <iwamatsu@...auri.org>,
<wendy.liang@...inx.com>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-fpga@...r.kernel.org>,
<git@...inx.com>, <chinnikishore369@...il.com>
Subject: [RFC v2 2/4] fpga: Add new property to support user-key encrypted bitstream loading
This patch Adds ‘encrypted-key-name’ property to
support user-key encrypted bitstream loading
use case.
Signed-off-by: Nava kishore Manne <nava.manne@...inx.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.
- 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.17.1
Powered by blists - more mailing lists