Received-SPF: pass (google.com: domain of linux-crypto+bounces-4457-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Maxime MERE <maxime.mere@foss.st.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
        "David S . Miller"
	<davem@davemloft.net>,
        Maxime Coquelin <mcoquelin.stm32@gmail.com>,
        Alexandre
 Torgue <alexandre.torgue@foss.st.com>
CC: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>,
        Rob
 Herring <robh@kernel.org>, <linux-crypto@vger.kernel.org>,
        <linux-stm32@st-md-mailman.stormreply.com>,
        <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
        =?UTF-8?q?Maxime=20M=C3=A9r=C3=A9?= <maxime.mere@foss.st.com>
Subject: [PATCH v3 0/4] crypto: stm32/cryp - Improve stm32-cryp driver
Date: Tue, 28 May 2024 16:05:44 +0200
Message-ID: <20240528140548.1632562-1-maxime.mere@foss.st.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

From: Maxime Méré <maxime.mere@foss.st.com>

This series of patches mainly aims to improve the usage of DMA with the
CRYP peripheral of the STM32 MPU series. The other two patches are
needed to enhance the driver's visibility for ST platforms.

This patchset version 3 addresses the issues identified by Herbert.
The code that raised a warning was in fact useless as there is already
an overflow check in the "stm32_cryp_dma_check" function so I removed
it.

I've also added a new patch that correct a spinlock recursion warning.

Maxime Méré (4):
  crypto: stm32/cryp - use dma when possible.
  crypto: stm32/cryp - increase priority
  crypto: stm32/cryp - add CRYPTO_ALG_KERN_DRIVER_ONLY flag
  crypto: stm32/cryp - call finalize with bh disabled

 drivers/crypto/stm32/stm32-cryp.c | 719 ++++++++++++++++++++++++++++--
 1 file changed, 674 insertions(+), 45 deletions(-)

-- 
2.25.1