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@xxxxxxxxxx> > --- > 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
