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: "Uwe Kleine-König" <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
Subject: [PATCH v2 0/3] crypto: stm32/cryp - Improve stm32-cryp driver
Date: Tue, 23 Apr 2024 17:14:06 +0200 [thread overview]
Message-ID: <20240423151409.902490-1-maxime.mere@foss.st.com> (raw)
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 v2 address the kernel robot warnings.
Maxime Méré (3):
crypto: stm32/cryp - use dma when possible.
crypto: stm32/cryp - increase priority
crypto: stm32/cryp - add CRYPTO_ALG_KERN_DRIVER_ONLY flag
drivers/crypto/stm32/stm32-cryp.c | 724 ++++++++++++++++++++++++++++--
1 file changed, 680 insertions(+), 44 deletions(-)
--
2.25.1
next reply other threads:[~2024-04-23 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 15:14 Maxime MERE [this message]
2024-04-23 15:14 ` [PATCH v2 1/3] crypto: stm32/cryp - use dma when possible Maxime MERE
2024-05-03 10:52 ` Herbert Xu
2024-04-23 15:14 ` [PATCH v2 2/3] crypto: stm32/cryp - increase priority Maxime MERE
2024-04-23 15:14 ` [PATCH v2 3/3] crypto: stm32/cryp - add CRYPTO_ALG_KERN_DRIVER_ONLY flag Maxime MERE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240423151409.902490-1-maxime.mere@foss.st.com \
--to=maxime.mere@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®