linux.git/drivers/crypto/rockchip, branch v6.6

crypto: drivers - Explicitly include correct DT includes

2023-08-23T03:04:23+00:00

The DT of_device.h and of_platform.h date back to the separate
of_platform_bus_type before it as merged into the regular platform bus.
As part of that merge prepping Arm DT support 13 years ago, they
"temporarily" include each other. They also include platform_device.h
and of.h. As a result, there's a pretty much random mix of those include
files used throughout the tree. In order to detangle these headers and
replace the implicit includes with struct declarations, users need to
explicitly include the correct includes.

Signed-off-by: Rob Herring 
Signed-off-by: Herbert Xu

crypto: rk3288 - Use new crypto_engine_op interface

2023-08-18T09:01:11+00:00

Use the new crypto_engine_op interface where the callback is stored
in the algorithm object.

Signed-off-by: Herbert Xu

crypto: rk3288 - Remove prepare/unprepare request

2023-08-18T09:01:09+00:00

The callbacks for prepare and unprepare request in crypto_engine
is superfluous.  They can be done directly from do_one_request.

Move the code into do_one_request and remove the unused callbacks.

Signed-off-by: Herbert Xu

crypto: rockchip - Remove surplus dev_err() when using platform_get_irq()

2022-11-11T10:14:59+00:00

There is no need to call the dev_err() function directly to print a
custom message when handling an error from either the platform_get_irq()
or platform_get_irq_byname() functions as both are going to display an
appropriate error message in case of a failure.

./drivers/crypto/rockchip/rk3288_crypto.c:351:2-9: line 351 is
redundant because platform_get_irq() already prints an error

Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2677
Reported-by: Abaci Robot 
Signed-off-by: Yang Li 
Acked-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - Add support for RK3399

2022-10-28T04:36:34+00:00

The RK3399 has 2 rk3288 compatible crypto device named crypto0 and
crypto1. The only difference is lack of RSA in crypto1.

We need to add driver support for 2 parallel instance as only one need
to register crypto algorithms.
Then the driver will round robin each request on each device.

For avoiding complexity (device bringup after a TFM is created), PM is
modified to be handled per request.
Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - permit to have more than one reset

2022-10-28T04:36:34+00:00

The RK3399 has 3 resets, so the driver to handle multiple resets.
This is done by using devm_reset_control_array_get_exclusive().

Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - rk_ahash_reg_init use crypto_info from parameter

2022-10-28T04:36:34+00:00

rk_ahash_reg_init() use crypto_info from TFM context, since we will
remove it, let's take if from parameters.

Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - Check for clocks numbers and their frequencies

2022-10-28T04:36:34+00:00

Add the number of clocks needed for each compatible.
Rockchip's datasheet give maximum frequencies for some clocks, so add
checks for verifying they are within limits. Let's start with rk3288 for
clock frequency check, other will came later.

Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - store crypto_info in request context

2022-10-28T04:36:34+00:00

The crypto_info to use must be stored in the request context.
This will help when 2 crypto_info will be available on rk3399.

Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu

crypto: rockchip - use the rk_crypto_info given as parameter

2022-10-28T04:36:33+00:00

Instead of using the crypto_info from TFM ctx, use the one given as parameter.

Reviewed-by: John Keeping 
Signed-off-by: Corentin Labbe 
Signed-off-by: Herbert Xu