HiSilicon Kunpeng 920 (Hi1620) True Random Number Generator
The hardware true random number generator block built into HiSilicon's Hi1620 server SoC, which powers Huawei's Kunpeng 920 ARM64 server processors. It feeds entropy into the kernel's crypto and random subsystems on Kunpeng-based servers and storage appliances that are still being sold and deployed today.
recommendation
It should stay in the kernel because the underlying Kunpeng 920 server platform is still shipping and being deployed in 2025, and the driver is actively maintained — a substantive fix was backported to stable as recently as 2026. While Kunpeng servers are a niche compared to mainstream x86 hardware, there is a real installed base that depends on this code for entropy.
repository signals
sources
- lore.kernel.org
The driver received a substantive 2026 fix/backport ('support tfms sharing the device'), showing ongoing maintenance rather than abandonment.
- cateee.net
LKDDb maps this driver to ACPI ID HISI02B3 and shows it still present in current kernel series, identifying it as the in-tree crypto driver for HiSilicon TRNG hardware.
- cateee.net
LKDDb identifies HISI02B3 / hisi-trng-v2 as the HiSilicon True Random Number Generator V2 found on the Hi1620 SoC, tying the driver to the Hi1620/Kunpeng generation.
- hikunpeng.com
Huawei's Kunpeng hardware FAQ states Kunpeng 920 supports hardware random number APIs and discusses current platform capabilities, indicating the RNG block is still relevant on deployed platforms.
- hikunpeng.com
Recent Kunpeng documentation lists verified environments on Kunpeng 920 and a 'new Kunpeng 920 processor model', evidence that this platform family remained in active use around 2025-2026.
codex reasoning notes (technical)
Local source inspection via shell `sed` showed ACPI HID `HISI02B3` and module name `hisi-trng-v2`, matching HiSilicon TRNG V2. `lore_activity` showed fresh 2026 stable backports for real fixes, with no evidence of removal activity. The LKDDb pages and HiKunpeng docs were obtained via `web.search_query`; they tie the driver to Hi1620/Kunpeng 920 and show the platform family still documented for current deployments. This is niche server silicon, so deployments are not broad consumer/high-volume, but they are still active enough to keep the driver.