All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Kim <david.kim@ncipher.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	Tim Magee <tim.magee@ncipher.com>
Subject: Re: [PATCH v2] drivers: misc: Add support for nCipher HSM devices
Date: Fri, 20 Dec 2019 22:30:36 +0100	[thread overview]
Message-ID: <20191220213036.GA27120@kroah.com> (raw)
In-Reply-To: <20191220154738.31448-1-david.kim@ncipher.com>

On Fri, Dec 20, 2019 at 03:47:38PM +0000, Dave Kim wrote:
> From: David Kim <david.kim@ncipher.com>
> 
> This is the driver for nCipher’s Solo and Solo XC hardware security modules.
> These modules implement a proprietary command set (the ’nCore API’) to
> perform cryptographic operations - key generation, signature, and so on. HSM
> commands and their replies are passed in a serialised binary format over the
> PCIe bus via a shared memory region. Multiple commands may be in-flight at
> any one time - command processing is multi-threaded and asynchronous. A write
> operation may, therefore, deliver multiple commands, and multiple replies may
> be retrieved in one read operation.

If this is "just" a crypto accelerator, why isn't this driver using the
existing in-kernel hardware crypto api?  What is lacking from it that
you need here?

thanks,

greg k-h

  reply	other threads:[~2019-12-20 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 15:47 [PATCH v2] drivers: misc: Add support for nCipher HSM devices Dave Kim
2019-12-20 21:30 ` Greg KH [this message]
2020-01-07  8:50   ` Kim, David
2020-01-07  9:28     ` Greg KH
2020-01-09  9:23       ` Kim, David
2020-01-09  9:36         ` Greg KH

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=20191220213036.GA27120@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=david.kim@ncipher.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.magee@ncipher.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.