Broadcom iProc SPU and SPU2 crypto accelerators
On-chip symmetric crypto offload engines built into Broadcom's iProc and Northstar2 networking system-on-chips, such as the BCM5871x and BCM58712. These parts went into volume production around 2016 and shipped in enterprise Ethernet switches, virtual customer-premises equipment, service routers, NAS boxes, and similar embedded networking gear.
recommendation
Worth keeping but flagging as niche legacy hardware. Upstream maintenance is genuinely active — the file received a substantive patch in February 2025 and the Kconfig symbol remains in current kernels — but the underlying SoCs are aging communications-grade chips from the mid-2010s, so real-world use is limited to existing embedded networking deployments rather than anything sold new today.
repository signals
sources
- lore.kernel.org
drivers/crypto/bcm/cipher.c received a substantive linux-crypto patch in February 2025, showing ongoing upstream maintenance rather than abandonment.
- cateee.net
CONFIG_CRYPTO_DEV_BCM_SPU remains present through current kernel series and matches DT compatibles brcm,spum-crypto, brcm,spum-nsp-crypto, brcm,spu2-crypto, and brcm,spu2-v2-crypto.
- investors.broadcom.com
Broadcom positioned BCM5871x as a communications/networking SoC family for vCPE, service routers, Ethernet-switch control planes, and NAS, with volume production announced in 2016.
- docs.broadcom.com
Broadcom's BCM958712D4XMC brief describes BCM58712 hardware-based crypto acceleration and targets enterprise switches, carrier access, edge computing, and data centers, indicating a niche embedded/networking deployment profile rather than mainstream new client hardware.
codex reasoning notes (technical)
Local source inspection via shell showed this is the Broadcom symmetric crypto offload platform driver with DT compatibles for SPUM/SPU2. lore_file_timeline on drivers/crypto/bcm/cipher.c showed steady 2022-2025 activity, including a 2025 fix and stable-tree inclusion, and did not surface removal-oriented traffic; that argues against deprecate/remove. Web search + open on Broadcom pages showed the attached SoC family is an older networking/control-plane product line first publicly volume-shipped in 2016 and documented in a 2018 reference-card brief, so 2025 deployments are likely niche/legacy embedded networking and low-volume rather than broad new sales. Because upstream maintenance is still real but deployment appears narrow and aging, keep the driver but annotate it as niche/legacy hardware. The 2025 sales-status=false field is an inference from searched public vendor evidence being old rather than an explicit EOL notice.