From: Richard Gong <richard.gong@linux.intel.com>
To: gregkh@linuxfoundation.org, mdf@kernel.org, trix@redhat.com,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: dinguyen@kernel.org, sridhar.rajagopal@intel.com, richard.gong@intel.com
Subject: Re: [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region
Date: Mon, 14 Dec 2020 08:03:07 -0600 [thread overview]
Message-ID: <8640e59d-5e38-a32a-2ac6-a178180e816d@linux.intel.com> (raw)
In-Reply-To: <1605709753-7800-1-git-send-email-richard.gong@linux.intel.com>
Hi Moritz, Greg,
Sorry for asking.
Any comment on Intel service layer and FPGA patches submitted on 11/18/20?
Regards,
Richard
On 11/18/20 8:29 AM, richard.gong@linux.intel.com wrote:
> From: Richard Gong <richard.gong@intel.com>
>
> This is 2nd submission of Intel service layer and FPGA patches.
>
> The customer wants to verify that a FPGA bitstream can be started properly
> before saving the bitstream to the QSPI flash memory.
>
> Bitstream authentication makes sure a signed bitstream has valid signatures.
>
> The customer sends the bitstream via FPGA framework and overlay, the
> firmware will authenticate the bitstream but not program the bitstream to
> device. If the authentication passes, the bitstream will be programmed into
> QSPI flash and will be expected to boot without issues.
>
> Extend Intel service layer, FPGA manager and region drivers to support the
> bitstream authentication feature.
>
> Richard Gong (5):
> firmware: stratix10-svc: add COMMAND_AUTHENTICATE_BITSTREAM flag
> fpga: fpga-mgr: add FPGA_MGR_BITSTREM_AUTHENTICATION flag
> fpga: of-fpga-region: add authenticate-fpga-config property
> dt-bindings: fpga: add authenticate-fpga-config property
> fpga: stratix10-soc: entend driver for bitstream authentication
>
> Documentation/devicetree/bindings/fpga/fpga-region.txt | 1 +
> drivers/fpga/of-fpga-region.c | 3 +++
> drivers/fpga/stratix10-soc.c | 3 +++
> include/linux/firmware/intel/stratix10-svc-client.h | 11 ++++++++---
> include/linux/fpga/fpga-mgr.h | 13 ++++++++-----
> 5 files changed, 23 insertions(+), 8 deletions(-)
>
next prev parent reply other threads:[~2020-12-14 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:29 [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region richard.gong
2020-11-18 14:29 ` [PATCHv2 1/5] firmware: stratix10-svc: add COMMAND_AUTHENTICATE_BITSTREAM flag richard.gong
2020-11-18 15:30 ` Moritz Fischer
2020-11-18 18:16 ` Richard Gong
2020-11-22 1:10 ` Moritz Fischer
2020-11-30 18:55 ` Richard Gong
2020-12-01 4:31 ` Moritz Fischer
2020-12-01 19:30 ` Richard Gong
2020-12-01 19:19 ` Moritz Fischer
2020-12-01 20:52 ` Richard Gong
2020-11-18 14:29 ` [PATCHv2 2/5] fpga: fpga-mgr: add FPGA_MGR_BITSTREM_AUTHENTICATION flag richard.gong
2020-11-18 14:29 ` [PATCHv2 3/5] fpga: of-fpga-region: add authenticate-fpga-config property richard.gong
2020-11-18 14:29 ` [PATCHv2 4/5] dt-bindings: fpga: " richard.gong
2020-11-18 14:29 ` [PATCHv2 5/5] fpga: stratix10-soc: extend driver for bitstream authentication richard.gong
2020-12-14 14:03 ` Richard Gong [this message]
2020-12-14 14:05 ` [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region Greg KH
2020-12-14 14:43 ` Richard Gong
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=8640e59d-5e38-a32a-2ac6-a178180e816d@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=richard.gong@intel.com \
--cc=sridhar.rajagopal@intel.com \
--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).