Samsung Exynos and Google Tensor SoC support blocks
SoC-level support code for Samsung Exynos application processors and Google's GS101 Tensor chip, covering things like chip identification, the Universal Serial Interface block that multiplexes UART/I2C/SPI, and similar low-level glue. These chips power Samsung phones and tablets, Samsung's Exynos Auto V9 automotive platform, and Google Pixel phones from roughly 2021 onward.
recommendation
It should stay in the kernel because these are active platform support drivers for current Samsung Exynos chips (including Exynos Auto V9, still marketed by Samsung in 2025) and Google's GS101 Tensor SoC used in Pixel phones. Upstream activity is healthy, with new GS101 chip-ID and OTP support landing in late 2025 and ongoing backports to stable trees. There is no replacement because these are chip-specific helpers rather than part of a generic framework.
repository signals
sources
- lore.kernel.org
Upstream gained new functionality for this directory in late 2025: exynos-chipid was extended for Google GS101 OTP support.
- lore.kernel.org
This directory still receives fixes/backports in maintained stable trees, indicating ongoing supported deployments.
- semiconductor.samsung.com
Samsung still markets Exynos Auto V9, a current automotive SoC explicitly matching this directory's EXYNOS_USI support text.
codex reasoning notes (technical)
Shell inspection shows real driver code under drivers/soc/samsung (module_platform_driver in exynos-chipid.c and exynos-usi.c; Kconfig names Exynos850 and ExynosAutoV9). lore_file_timeline was used on exynos-chipid.c and exynos-usi.c: it showed substantial 2025 activity, including new GS101 support and stable backports, which argues against deprecation. Web search found Samsung's official Exynos Auto V9 product page, supporting that at least part of the covered hardware family was still sold/new in 2025. No natural replacement exists because these are SoC-specific support drivers rather than a superseded generic stack.