summaryrefslogtreecommitdiffstats
path: root/drivers/s390/crypto/zcrypt_cex2a.c
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2006-09-20 15:58:27 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2006-09-20 15:58:27 +0200
commit2dbc2418bac32a18a372ae9aec386f0fe9174389 (patch)
treeedfbdc374bc636021aa084c95bd77b49f3a1a1bb /drivers/s390/crypto/zcrypt_cex2a.c
parent1534c3820c26aca4e2567f97b8add8bea40e7e2b (diff)
downloadop-kernel-dev-2dbc2418bac32a18a372ae9aec386f0fe9174389.zip
op-kernel-dev-2dbc2418bac32a18a372ae9aec386f0fe9174389.tar.gz
[S390] zcrypt user space interface.
The user space interface of the zcrypt device driver implements the old user space interface as defined by the old z90crypt driver. Everything is there, the /dev/z90crypt misc character device, all the lovely ioctls and the /proc file. Even writing to the z90crypt proc file to configure the crypto device still works. It stands to reason to remove the proc write function someday since a much cleaner configuration via the sysfs is now available. The ap bus device drivers register crypto cards to the zcrypt user space interface. The request router of the user space interface picks one of the registered cards based on the predicted latency for the request and calls the driver via a callback found in the zcrypt_ops of the device. The request router only knows which operations the card can do and the minimum / maximum number of bits a request can have. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> Signed-off-by: Ralph Wuerthner <rwuerthn@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/s390/crypto/zcrypt_cex2a.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud