linux-toradex.git/drivers/crypto/hisilicon, branch master

hwrng: hisi-trng - Move hisi-trng into drivers/char/hw_random/

2026-06-11T06:02:58+00:00

Since this file just implements a hwrng driver, move it into
drivers/char/hw_random/.  Rename the kconfig option accordingly as well.

Note that this moves the file back to its original location.

Signed-off-by: Eric Biggers 
Signed-off-by: Herbert Xu

crypto: hisi-trng - Remove crypto_rng interface

2026-06-11T05:53:59+00:00

drivers/crypto/hisilicon/trng/trng.c exposes the same hardware through
two completely separate interfaces, crypto_rng and hwrng.  However, the
implementation of this is buggy because it permits generation operations
from these interfaces to run concurrently with each other, accessing the
same registers.  That is, hisi_trng_generate() synchronizes with itself
but not with hisi_trng_read().  This results in potential repetition of
output from the RNG, output of non-random values, etc.

Fortunately, there's actually no point in hardware RNG drivers
implementing the crypto_rng interface.  It's not actually used by
anything besides the "rng" algorithm type of AF_ALG, which in turn is
not actually used in practice.  Other crypto_rng hardware drivers are
likewise being phased out, leaving just the hwrng support.

Thus, remove it to simplify the code and avoid conflict (and confusion)
with the hwrng interface which is the one that actually matters.

Fixes: e4d9d10ef4be ("crypto: hisilicon/trng - add support for PRNG")
Cc: stable@vger.kernel.org
Signed-off-by: Eric Biggers 
Signed-off-by: Herbert Xu

crypto: hisilicon/qm - support doorbell enable control

2026-05-29T05:54:43+00:00

The driver notifies the hardware to handle task through
doorbell. Currently, doorbell is enabled by default. To
prevent the process from sending doorbells during hardware
reset scenarios, which could cause the hardware to process
doorbells and trigger new errors:

For example, when the physical machine is resetting the device,
doorbells are still being sent from the virtual machine.

Therefore, the driver disables doorbell during hardware
unavailability. After hardware initialization is completed,
doorbell is enabled, and any task sent during the unavailability
period will return errors.

The hardware supports the PF to disable doorbells for all functions,
while the VF can only disable its own doorbell function. When the PF
is reset, it will disable doorbells for all functions. When VF is
reset, it only disables its own doorbell and does not affect tasks
on other functions.

Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon - mask all error type when removing driver

2026-05-29T05:54:43+00:00

Each bit in the error interrupt register corresponds to a specific
error type. A bit value of 0 enables the interrupt, and a bit value
of 1 disables the interrupt. Currently, when disabling interrupts,
it incorrectly enables the interrupt types that were not enabled.
Therefore, when disabling interrupts, all bits should be directly
written to 1.

Signed-off-by: Weili Qian 
Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon/qm - disable error report before flr

2026-05-29T05:54:43+00:00

Before function level reset, driver first disable device error report
and then waits for the device reset to complete. However, when the
error is recovered, the error bits will be enabled again, resulting in
invalid disable. It is modified to detect that there is no error
before disable error report, and then do FLR.

Fixes: 7ce396fa12a9 ("crypto: hisilicon - add FLR support")
Signed-off-by: Weili Qian 
Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon/qm - support function-level error reset

2026-05-29T05:54:43+00:00

When executing operations on crypto devices, hardware errors
are inevitable. For certain errors, a full device reset is
required to recover. However, in certain cases, only a
specific function may fail, while other functions can still
operate normally. A system-wide RAS reset in such cases would
unnecessarily impact functioning components.

This patch introduces function-level granularity handling,
enabling targeted resets of only the error-reporting
functions without affecting other operational functions.

Signed-off-by: Zhushuai Yin 
Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon/qm - place the interrupt status interface after the PM usage counter

2026-05-29T05:54:43+00:00

To avoid accessing memory of a suspended device, and since the counter
interface used by PM involves sleep operations, the counter interface
cannot be placed in the interrupt top half. Therefore, the interface for
acquiring the interrupt status in the RAS reset flow that resides in the
interrupt context needs to be moved to the bottom half for processing.

Signed-off-by: Zhushuai Yin 
Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon/qm - allow VF devices to query hardware isolation status

2026-05-29T05:54:43+00:00

The problem that the VF device cannot obtain the isolation
status and isolation threshold of the device is resolved.

The accelerator driver can query the device isolation status
and threshold via the VF device using the fault query sysfs
interface under uacce. Note that only the PF device supports
isolation policy configuration, while the VF device is
limited to read-only query operations.

Signed-off-by: Zhushuai Yin 
Signed-off-by: Zongyu Wu 
Signed-off-by: Herbert Xu

crypto: hisilicon/sec2 - lower priority for hisilicon crypto implementations

2026-05-22T12:25:28+00:00

Lower the priority of HiSilicon's crypto implementations to allow more
suitable alternatives to be selected. For example, certain kernel
use-cases do not benefit from HiSilicon's symmetric crypto algorithms.
This change ensures that more appropriate options are chosen first while
retaining HiSilicon's implementations as alternatives.

Signed-off-by: lizhi 
Signed-off-by: Chenghai Huang 
Reviewed-by: Longfang Liu 
Signed-off-by: Herbert Xu

crypto: hisilicon - Fix dma_unmap_single() direction

2026-04-12T08:46:29+00:00

The direction used to map the buffer skreq->iv is DMA_TO_DEVICE but it is
unmapped with direction DMA_BIDIRECTIONAL in the error path.

Change the unmap to match the mapping.

Fixes: 915e4e8413da ("crypto: hisilicon - SEC security accelerator driver")
Cc: 
Signed-off-by: Thomas Fourier 
Reviewed-by: Thorsten Blum 
Signed-off-by: Herbert Xu