On Fri, Mar 13, 2020 at 09:48:14AM +0000, Kim, David wrote: > Hi Herbert, > > We've been working on getting this driver code upstreamed into drivers/misc since the end of last > year but things stalled a bit on our end. However, we are still interested in getting our submission > approved and would please like your assistance and feedback on this. > > The driver code for the hardware is straightforward and does not contain any cryptographic > components as the cryptography is handled within the hardware's secure boundary. We have no > plans to use the linux kernel crypto APIs as our customers require compliance to the FIPS 140 > standard or the eIDAS regulations. But what I said was, you NEED to use the linux kernel crypto apis as you need to not try to create your own. Just because this is the way you did it before, does not mean it is the correct thing to do. So what is wrong if you do use the existing apis? What is preventing you from doing that? thanks, greg k-h
