diff options
author | Adam Guerin <adam.guerin@intel.com> | 2023-09-14 15:14:13 +0100 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2023-09-20 13:15:54 +0800 |
commit | 37b14f2dfa791fd485dbc536f8d1ffe8c6990290 (patch) | |
tree | 3a730c61964d38a689c6e3d6d22b9ad61c08e104 /lib/find_bit.c | |
parent | 71713766380712c8ab2d604605e7b0b20f977801 (diff) | |
download | linux-stable-37b14f2dfa791fd485dbc536f8d1ffe8c6990290.tar.gz linux-stable-37b14f2dfa791fd485dbc536f8d1ffe8c6990290.tar.bz2 linux-stable-37b14f2dfa791fd485dbc536f8d1ffe8c6990290.zip |
crypto: qat - enable dc chaining service
QAT GEN4 devices support chained compression operations. These
allow, with a single request to firmware, to hash then compress
data.
Extend the configuration to enable such mode. The cfg_services
operations in sysfs are extended to allow the string "dcc". When
selected, the driver downloads to the device both the symmetric
crypto and the compression firmware images and sends an admin message
to firmware which enables `chained` operations.
In addition, it sets the device's capabilities as the combination
of compression and symmetric crypto capabilities, while excluding
the ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC bit to indicate
that in this mode, symmetric crypto instances are not supported.
When "dcc" is enabled, the device will handle compression requests
as if the "dc" configuration is loaded ("dcc" is a variation of "dc")
and the driver will register the acomp algorithms.
As for the other extended configurations, "dcc" is only available for
qat_4xxx devices and the chaining service will be only accessible from
user space.
Signed-off-by: Adam Guerin <adam.guerin@intel.com>
Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'lib/find_bit.c')
0 files changed, 0 insertions, 0 deletions