From: Greg KH <gregkh@linuxfoundation.org> To: Nava kishore Manne <navam@xilinx.com> Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>, Michal Simek <michals@xilinx.com>, "mdf@kernel.org" <mdf@kernel.org>, "trix@redhat.com" <trix@redhat.com>, "arnd@arndb.de" <arnd@arndb.de>, Rajan Vaja <RAJANV@xilinx.com>, Amit Sunil Dhamne <amitsuni@xlnx.xilinx.com>, Tejas Patel <tejasp@xlnx.xilinx.com>, "zou_wei@huawei.com" <zou_wei@huawei.com>, Sai Krishna Potthuri <lakshmis@xilinx.com>, Ravi Patel <ravipate@xlnx.xilinx.com>, "iwamatsu@nigauri.org" <iwamatsu@nigauri.org>, Jiaying Liang <jliang@xilinx.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>, git <git@xilinx.com>, "chinnikishore369@gmail.com" <chinnikishore369@gmail.com> Subject: Re: [RFC v2 1/4] drivers: firmware: Add user encrypted key load API support Date: Fri, 9 Jul 2021 11:49:27 +0200 [thread overview] Message-ID: <YOgbp79NQeN6K1e1@kroah.com> (raw) In-Reply-To: <PH0PR02MB7336410E513B4D026BB4983EC2189@PH0PR02MB7336.namprd02.prod.outlook.com> On Fri, Jul 09, 2021 at 08:41:35AM +0000, Nava kishore Manne wrote: > Hi Greg, > > Thanks for providing the review comments. > Please find my response inline. > > > -----Original Message----- > > From: Greg KH <gregkh@linuxfoundation.org> > > Sent: Wednesday, June 9, 2021 3:25 PM > > To: Nava kishore Manne <navam@xilinx.com> > > Cc: robh+dt@kernel.org; Michal Simek <michals@xilinx.com>; > > mdf@kernel.org; trix@redhat.com; arnd@arndb.de; Rajan Vaja > > <RAJANV@xilinx.com>; Amit Sunil Dhamne <amitsuni@xlnx.xilinx.com>; > > Tejas Patel <tejasp@xlnx.xilinx.com>; zou_wei@huawei.com; Sai Krishna > > Potthuri <lakshmis@xilinx.com>; Ravi Patel <RAVIPATE@xilinx.com>; > > iwamatsu@nigauri.org; Jiaying Liang <jliang@xilinx.com>; > > devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux- > > kernel@vger.kernel.org; linux-fpga@vger.kernel.org; git <git@xilinx.com>; > > chinnikishore369@gmail.com > > Subject: Re: [RFC v2 1/4] drivers: firmware: Add user encrypted key load API > > support > > > > On Wed, Jun 09, 2021 at 11:22:29AM +0530, Nava kishore Manne wrote: > > > This patch adds user encrypted key load API to support User key > > > encrypted images loading use cases from Linux. > > > > What is "user key encrypted images"? Do we need more documentation > > here for what this is and how to use it? > > > > Xilinx bitstream writer, using AES, encrypts the bitstream. This feature allows user to encrypt bitstream using 256-bit AES encryption in cipher block chaining (CBC) mode. > User can supply a 128-bit Initial Vector and 256-bit key(user key). Please provide the needed information in the changelog comment. > For more info please refer here: > https://www.xilinx.com/support/documentation/application_notes/xapp1239-fpga-bitstream-encryption.pdf External links always grow stale. thanks, greg k-h
next prev parent reply other threads:[~2021-07-09 9:49 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 [this message] 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 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=YOgbp79NQeN6K1e1@kroah.com \ --to=gregkh@linuxfoundation.org \ --cc=RAJANV@xilinx.com \ --cc=amitsuni@xlnx.xilinx.com \ --cc=arnd@arndb.de \ --cc=chinnikishore369@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=git@xilinx.com \ --cc=iwamatsu@nigauri.org \ --cc=jliang@xilinx.com \ --cc=lakshmis@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=michals@xilinx.com \ --cc=navam@xilinx.com \ --cc=ravipate@xlnx.xilinx.com \ --cc=robh+dt@kernel.org \ --cc=tejasp@xlnx.xilinx.com \ --cc=trix@redhat.com \ --cc=zou_wei@huawei.com \ --subject='Re: [RFC v2 1/4] drivers: firmware: Add user encrypted key load API support' \ /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
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).