From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
Lionel Debieve <lionel.debieve@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2] crypto: stm32 - remove crc32 and crc32c support
Date: Sun, 8 Jun 2025 16:44:58 -0700 [thread overview]
Message-ID: <20250608234458.GD1259@sol> (raw)
In-Reply-To: <20250601193441.6913-1-ebiggers@kernel.org>
On Sun, Jun 01, 2025 at 12:34:41PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Remove the crc32 and crc32c support from the stm32 driver. Since it's
> not wired up to the CRC library, almost no CRC user in the kernel can
> actually be taking advantage of it, so it's effectively dead code.
>
> Support for this hardware could be migrated to the CRC library, but
> there doesn't seem to be much point. This CRC engine is present only on
> a couple older SoCs that lacked CRC instructions.
>
> Even on those SoCs, it's probably not worthwhile. This driver has to
> deal with things like locking and runtime power management that do not
> exist in software CRC code and are a source of bugs (as is clear from
> the commit log) and add significant overhead to the processing of short
> messages, which are common. The patch that originally added this driver
> seemed to justify it based purely on a microbenchmark on Cortex-M7 on
> long messages, not a real use case. These days, if this driver were to
> be used at all it would likely be on Cortex-A7 instead. This CRC engine
> is also not supported by QEMU, making the driver not easily testable.
>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Fabien Dessenne <fabien.dessenne@foss.st.com>
> Cc: Lionel Debieve <lionel.debieve@foss.st.com>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>
> v2: reworked commit message and added Acked-by
>
> arch/arm/configs/multi_v7_defconfig | 1 -
> drivers/crypto/stm32/Kconfig | 9 -
> drivers/crypto/stm32/Makefile | 1 -
> drivers/crypto/stm32/stm32-crc32.c | 480 ----------------------------
> 4 files changed, 491 deletions(-)
> delete mode 100644 drivers/crypto/stm32/stm32-crc32.c
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
Adjusted wording in commit message slightly:
"Even on those SoCs, it's probably not worthwhile."
=>
"Even for those SoCs, it probably wouldn't be worthwhile."
... since it's talking about a hypothetical port to the CRC library, not the
status quo where the driver is almost never used anyway.
- Eric
prev parent reply other threads:[~2025-06-08 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 19:34 [PATCH v2] crypto: stm32 - remove crc32 and crc32c support Eric Biggers
2025-06-04 8:38 ` Arnd Bergmann
2025-06-08 23:44 ` Eric Biggers [this message]
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=20250608234458.GD1259@sol \
--to=ebiggers@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=fabien.dessenne@foss.st.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@foss.st.com \
--cc=mcoquelin.stm32@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.