On Mon, 8 Mar 2021 at 06:42, Herbert Xu wrote:
>
> On Sun, Feb 28, 2021 at 03:14:55AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head: 5695e51619745d4fe3ec2506a2f0cd982c5e27a4
> > commit: a4397635afea5d127548d64e
On 3/5/21 3:59 PM, Stefan Berger wrote:
diff --git a/crypto/Kconfig b/crypto/Kconfig
index a367fcfeb5d4..a31df40591f5 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -247,6 +247,16 @@ config CRYPTO_ECDH
help
Generic implementation of the ECDH algorithm
@@ -70,6 +72,30 @@
From: Vaibhav Gupta
This patch series aims to modify necessary files before an entry for sa2ul
can be made in the respective am64 device tree.
Peter Ujfalusi (3):
dt-bindings: crypto: ti,sa2ul: Add new compatible for AM64
crypto: sa2ul: Support for per channel coherency
crypto: sa2ul: Add
From: Peter Ujfalusi
On AM64 the DMA channel for sa2ul can be configured to be coherent or
non coherent via DT binding.
Use the dmaengine_get_device_for_dma_api() to get the device pointer which
should be used for with the dma_api to use matching dma_ops for the
channel coherency/non coherency.
From: Peter Ujfalusi
Add the AM64 version of sa2ul to the compatible list.
[v_gu...@ti.com: Conditional dma-coherent requirement, clocks]
Signed-off-by: Peter Ujfalusi
Signed-off-by: Vaibhav Gupta
---
.../devicetree/bindings/crypto/ti,sa2ul.yaml | 40 +++
1 file changed, 33 i
From: Peter Ujfalusi
The sa2ul module in am64 have limited support for algorithms, and the
priv and priv_id used on the platform is different compared to AM654 or
j721e.
Use match data to get the SoC specific information and use it throughout
the driver.
Signed-off-by: Peter Ujfalusi
Signed-of
On Fri, 05 Mar 2021 08:01:30 +0100, Álvaro Fernández Rojas wrote:
> brcm,bcm6368-rng controllers require enabling the IPSEC clock in order to get
> a functional RNG.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: add new patch making clocks mandatory for BCM6368.
>
> .../devicetree/bind
On Fri, 05 Mar 2021 08:01:31 +0100, Álvaro Fernández Rojas wrote:
> brcm,bcm6368-rng controllers require resetting the IPSEC clock in order to get
> a functional RNG.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: fix dt-bindings warnings.
> v5: no changes.
> v4: pass dt_binding_check.
On 3/4/21 11:01 PM, Álvaro Fernández Rojas wrote:
> BCM6368 devices need to reset the IPSEC controller in order to generate true
> random numbers.
>
> This is what BCM6368 produces without a reset:
> root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
> rngtest 6.10
> Copyright (c) 2004 by Henrique d
On 3/4/21 11:01 PM, Álvaro Fernández Rojas wrote:
> brcm,bcm6368-rng controllers require resetting the IPSEC clock in order to get
> a functional RNG.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
On 3/4/21 11:01 PM, Álvaro Fernández Rojas wrote:
> brcm,bcm6368-rng controllers require enabling the IPSEC clock in order to get
> a functional RNG.
>
> Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
--
Florian
Le Thu, Mar 04, 2021 at 05:57:17PM -0800, Jia-Ju Bai a écrit :
> When dma_mapping_error() returns an error, no error return code of
> sun8i_ce_prng_generate() is assigned.
> To fix this bug, err is assigned with -EFAULT as error return code.
>
> Reported-by: TOTE Robot
> Signed-off-by: Jia-Ju Ba
Le Tue, Mar 02, 2021 at 04:34:46PM +, Colin King a écrit :
> From: Colin Ian King
>
> In the case where the dma_iv mapping fails, the return error path leaks
> the memory allocated to object d. Fix this by adding a new error return
> label and jumping to this to ensure d is free'd before the
13 matches
Mail list logo
