drivers/soc/fujitsu

Fujitsu A64FX HPC platform diagnostic support

Platform glue for Fujitsu's A64FX Arm processor, the 48-core CPU that powered the Fugaku supercomputer and continues to ship in Fujitsu PRIMEHPC FX1000 and FX700 systems. Specifically, it lets the baseboard management controller signal the OS to take a diagnostic panic and kernel dump when something goes wrong on the node.

keep-annotate conf=0.78 deploy=low replacement=none subsystem=soc category=platform-vendor
78%

recommendation

Worth keeping but flagging as narrowly scoped: the code only matters on Fujitsu A64FX HPC nodes, which are still sold in 2025 but deployed in a small number of supercomputing sites rather than general-purpose servers. It was added in 2022, has seen only a handful of commits (most recently routine 2024 API cleanups, not removal proposals), and there is no replacement because the functionality is specific to the A64FX baseboard management controller.

repository signals

3 files
151 source lines
5 commits, 5y
+177 / −7 lines added / removed, 5y
5 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 5 total · active in 5/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +173 −0 2022-06: 0 commits · +0 −0 2022-07: 1 commit · +1 −1 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 1 commit · +0 −1 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +2 −4 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 1 commit · +1 −1 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Driver was added in 2022 specifically for A64FX diagnostic interrupts triggered via the BMC to force panic/kernel-dump collection.

  2. lore.kernel.org

    The most recent upstream touch in late 2024 was routine platform-driver API maintenance, indicating the code is still being kept buildable rather than being discussed for removal.

  3. fujitsu.com

    Fujitsu still markets the A64FX processor on a current product page and positions it as the CPU for Fujitsu/HPE HPC platforms.

  4. fujitsu.com

    Current Fujitsu PRIMEHPC FX1000 and FX700 specification pages list A64FX as the CPU, supporting that new-system sales/deployments persisted into the present web snapshot.

codex reasoning notes (technical)

Local shell inspection (`sed`) showed this is a real platform driver (`a64fx-diag.c`) for ACPI ID `FUJI2007`, enabling BMC-triggered diagnostic panic/NMI handling on Fujitsu A64FX systems. Local `git -c safe.directory ... log/show` found only 5 substantive commits since introduction, with late-2023/2024 touches being treewide platform callback conversions, not removal work; the cited lore URLs were obtained from those commit messages. Web search found Fujitsu's current A64FX product page and current PRIMEHPC specs page, which together indicate A64FX hardware remains sold in niche HPC form factors. Deployment is therefore niche but real, with no natural replacement driver because this functionality is A64FX/BMC-specific. Keep the driver, but annotate as narrow HPC-specific coverage rather than broadly deployed hardware.