> > + ret = clk_set_rate(qce->core_src, 1);
>
> Could you point me from where you got this number?
I got it from codeaurora qce driver:
https://android.googlesource.com/kernel/msm/+/android-msm-hammerhead-3.4-kk-r1/drivers/crypto/msm/qce50.c#3386
--
To unsubscribe from this list:
Without that, QCE performance is about 2x less.
Signed-off-by: Iaroslav Gridin <voke...@gmail.com>
---
drivers/crypto/qce/core.c | 18 +-
drivers/crypto/qce/core.h | 2 +-
2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/qce/core.c b/drivers/
From: Voker57 <voke...@gmail.com>
Current code avoids supplying scatterlist containing more data than used
to DMA. This leads to dropping data from scatterlists which would
leave some for next run.
Signed-off-by: Iaroslav Gridin <voke...@gmail.com>
---
drivers/crypto/qce/sha.c |
From: Voker57 <voke...@gmail.com>
Zero-sized updates lock QCE, so ensure there's always some data left
for the final update, up to blocksize.
Signed-off-by: Iaroslav Gridin <voke...@gmail.com>
---
drivers/crypto/qce/sha.c | 30 --
1 file changed, 20 inser
From: Voker57 <voke...@gmail.com>
Calling QCE finalization when hash have already been finalized causes
a lockup. Avoid it by introducing finalized flag.
Signed-off-by: Iaroslav Gridin <voke...@gmail.com>
---
drivers/crypto/qce/sha.c | 6 ++
drivers/crypto/qce/sha.h | 1 +
2 file
