NXP i.MX95 System Manager SCMI vendor protocols
NXP-specific extensions to the Arm SCMI firmware interface used on the i.MX95 family of application processors, where a dedicated System Manager core handles power, clocks, battery-backed memory, and other shared resources on behalf of the Linux-running cores. The i.MX95 is a current NXP SoC aimed at automotive, industrial, and IoT designs.
recommendation
It should stay in the kernel because the i.MX95 is an active NXP product line still being sold into automotive, industrial, and IoT designs in 2025, and the code is receiving steady upstream care: it landed in 2024, picked up bug fixes in early 2025, gained CPU and logical-machine-management features through 2025, and has more work queued for 2026. Because these are vendor-specific SCMI protocol extensions rather than a generic interface, nothing else in the tree could replace them.
repository signals
sources
- nxp.com
NXP lists i.MX95 as Active, with buy/parametrics, 2026 documentation updates, and current target markets in automotive/industrial/IoT.
- git.zx2c4.com
The upstream SCMI 6.12 merge added the i.MX vendor SCMI directory and initial BBM/MISC support plus i.MX95 SCMI documentation.
- lists.infradead.org
A 2025 SCMI fix pull request included a bug fix for scmi_imx_misc_ctrl_set, showing post-merge maintenance rather than removal.
codex reasoning notes (technical)
Real driver directory, not a helper: local shell `rg` found `module_scmi_protocol(...)` registrations in the four C files, and local `sed` of `imx95.rst` identified the scope as i.MX95 System Manager vendor SCMI protocols. Upstream activity is healthy: local `git -c safe.directory=... log` showed initial landing in 2024-08, fixes in 2025-01, CPU/LMM expansion in 2025-04, more MISC feature work in 2025-09/10, and a 2026 merge; web-obtained URLs corroborate initial upstream merge and 2025 bug-fix traffic. NXP's product page was obtained via web search/open and shows i.MX95 is still an active product family, so hardware is still sold and new deployments remain plausible, though this specific SCMI extension stack is niche to i.MX95 mixed-core/system-manager designs. No natural replacement driver exists because these are vendor-specific SCMI protocol implementations rather than a superseded generic path; no removal discussion was found in the lore-targeted web searches used here.