SPI is a simple four-wire serial bus invented by Motorola in the 1980s and ubiquitous in embedded systems. This directory holds the Linux SPI core plus dozens of host-controller drivers that let the kernel talk to flash memory, sensors, small displays, and touch controllers on boards ranging from Raspberry Pi-class hardware to current Microchip SAMA7 and STM32 SoCs.
It should stay because SPI is one of the most common low-speed buses in modern hardware, used to wire up flash chips, sensors, displays, and radios on embedded boards from vendors like Apple, AMD, STM32, Microchip, and Rockchip. The subsystem is actively maintained, with new controller drivers and core changes still landing in 2026, and there is no replacement framework on the horizon.
repository signals
182files
130,747source lines
2,303commits, 5y
+59,639 / −22,810lines added / removed, 5y
460authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 2,303 total · active in 61/61 months
`drivers/spi/spi.c` was still receiving upstream feature work in April 2026, indicating an actively maintained subsystem rather than a retirement candidate.
Kernel documentation describes SPI as a first-class Linux subsystem covering controller and protocol drivers, reflecting ongoing supported use across embedded systems.
Microchip lists the SAMA7G54 MPU as `Status: In Production`; the SAMA7 family is a current Linux-capable embedded platform that uses SPI/QSPI-class storage and peripherals.
codex reasoning notes (technical)
`drivers/spi` is the SPI subsystem directory, with core code plus many active controller/protocol drivers, not a single obsolete leaf. Lore evidence came from `lore_file_timeline` on `drivers/spi/spi.c`, which showed recent 2026 traffic and sustained yearly patch volume; no removal signal was found in the sampled lore checks. The kernel-docs and Microchip URLs were obtained via `web.search_query`. Local inspection of `drivers/spi/Kconfig` showed current platform coverage (for example Apple, AMD, STM32, Microchip, Rockchip, virtio), reinforcing that new deployments remain common. SPI itself is still pervasive in new embedded/industrial designs, so this should be kept; there is no natural replacement driver for the subsystem as a whole.