On Wed, Feb 15, 2017 at 9:03 AM, Michal Simek <[email protected]> wrote: > On 15.2.2017 01:31, [email protected] wrote: >> From: Moritz Fischer <[email protected]> >> >> Add a flag that is passed to the write_init() callback, indicating >> that the bitstream is encrypted. >> >> The low-level driver will deal with the flag, or return an error, >> if encrypted bitstreams are not supported. >> >> Signed-off-by: Moritz Fischer <[email protected]> >> Cc: Alan Tull <[email protected]> >> Cc: Michal Simek <[email protected]> >> Cc: Sören Brinkmann <[email protected]> >> Cc: [email protected] >> Cc: [email protected] >> --- >> include/linux/fpga/fpga-mgr.h | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/include/linux/fpga/fpga-mgr.h b/include/linux/fpga/fpga-mgr.h >> index 57beb5d..1355d8a 100644 >> --- a/include/linux/fpga/fpga-mgr.h >> +++ b/include/linux/fpga/fpga-mgr.h >> @@ -70,6 +70,7 @@ enum fpga_mgr_states { >> */ >> #define FPGA_MGR_PARTIAL_RECONFIG BIT(0) >> #define FPGA_MGR_EXTERNAL_CONFIG BIT(1) >> +#define FPGA_MGR_DECRYPT_BITSTREAM BIT(2) >> >> /** >> * struct fpga_image_info - information specific to a FPGA image >> > > Isn't it better to state that bitstream is encrypted > instead of saying that bitstream requires decryption?
Such as FPGA_MGR_ENCRYPTED_BITSTREAM ? Also please consider adding a DT property such that the FPGA region code will set this flag similar to how the DTO sets up other FPGA image info. Alan > > Your second patch is saying add support for encrypted bitstreams. > > M > > -- > To unsubscribe from this list: send the line "unsubscribe linux-fpga" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html
