linux-drivers/
drivers/net/can/flexcan

NXP/Freescale FlexCAN controller for i.MX and S32 SoCs

FlexCAN is the CAN and CAN FD bus controller built into many NXP and former Freescale microcontrollers and application processors, including the i.MX, Vybrid, LayerScape, and S32 automotive families. It connects Linux systems to vehicle networks, factory floor equipment, and other embedded controllers that speak CAN, and it is still appearing in NXP silicon shipping in 2025.

keep conf=0.91 deploy=medium replacement=none subsystem=net category=networking-other
91%

recommendation

It should stay because FlexCAN is the only in-tree driver for an NXP IP block that ships in current automotive and industrial SoCs like the i.MX95 and S32G2/S32G3, and upstream work in 2024 added wakeup support and new SoC enablement. There is no replacement to migrate to and the hardware is still sold new in 2025.

repository signals

4 files
2,737 source lines
32 commits, 5y
+3,062 / −318 lines added / removed, 5y
13 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 32 total · active in 19/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: 7 commits · +2,813 −163 2022-02: 0 commits · +0 −0 2022-03: 1 commit · +2 −2 2022-04: 1 commit · +4 −8 2022-05: 1 commit · +0 −7 2022-06: 0 commits · +0 −0 2022-07: 2 commits · +4 −8 2022-08: 2 commits · +43 −43 2022-09: 1 commit · +1 −2 2022-10: 0 commits · +0 −0 2022-11: 2 commits · +37 −4 2022-12: 1 commit · +9 −3 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +2 −4 2023-06: 1 commit · +2 −2 2023-07: 2 commits · +19 −41 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +2 −10 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: 1 commit · +45 −7 2024-09: 1 commit · +1 −1 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 2 commits · +39 −1 2025-02: 0 commits · +0 −0 2025-03: 3 commits · +37 −9 2025-04: 0 commits · +0 −0 2025-05: 1 commit · +2 −2 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: 1 commit · +0 −1 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. spinics.net

    July 23, 2024 patch series adds i.MX95 wakeup support to flexcan, showing active upstream enablement for a new NXP SoC generation.

  2. lkml.org

    November 25, 2024 patch series adds FlexCAN support for NXP S32G2/S32G3 SoCs, indicating ongoing upstream expansion rather than retirement.

  3. nxp.com

    NXP lists the i.MX95 family as active/current and its product details include 5x CAN FD, matching ongoing FlexCAN-backed new-platform deployment.

  4. nxp.com

    NXP lists S32G2 as active/current, with Linux BSP support and vehicle-networking positioning, supporting continued real-world FlexCAN deployments.

codex reasoning notes (technical)

Real driver directory confirmed by local code inspection with exec_command: platform driver entry, OF match table, and multiple SoC compatibles in flexcan-core.c. Upstream activity checked via exec_command git log on the directory: multiple substantive 2024-2025 fixes/features, including PM work and new SoC support; no removal-oriented history surfaced. URLs were obtained by web search: spinics/LKML patch threads show active feature work for i.MX95 and S32G2/S32G3, and NXP product pages show the IP remains present in active i.MX95 and S32G2 products sold for industrial/automotive use. No natural in-tree replacement exists because this is the vendor-specific driver for the FlexCAN IP block.