drivers/soc/tegra/cbb

NVIDIA Tegra and Grace Control Backbone (CBB) error reporting

Handles the Control Backbone, the on-chip interconnect fabric inside NVIDIA's modern Tegra SoCs (Tegra194, Tegra234, Tegra241 and newer), reporting bus errors and access violations between CPU clusters, accelerators, and peripherals. It underpins reliability and debugging on current Jetson Orin embedded boards and Grace CPU Superchip server platforms.

keep conf=0.94 deploy=medium replacement=none subsystem=soc category=platform-vendor
94%

recommendation

It should stay in the kernel because it serves current NVIDIA hardware that is actively shipping in 2025, including Jetson Orin embedded modules (Tegra234) and Grace CPU Superchip data-center systems (Tegra241). Upstream activity is healthy: maintainers added support for newer Tegra254 and Tegra264 chips as recently as July 2025, and there is no replacement driver since this reports faults from a fabric internal to the SoC itself.

repository signals

4 files
4,134 source lines
27 commits, 5y
+4,486 / −343 lines added / removed, 5y
13 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 27 total · active in 15/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: 3 commits · +3,678 −2 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 2 commits · +2 −15 2022-10: 1 commit · +1 −3 2022-11: 4 commits · +147 −39 2022-12: 1 commit · +0 −6 2023-01: 0 commits · +0 −0 2023-02: 1 commit · +0 −2 2023-03: 1 commit · +0 −3 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +2 −6 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +1 −10 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: 1 commit · +1 −1 2025-01: 1 commit · +4 −16 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: 7 commits · +646 −234 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 1 commit · +1 −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. git.kernel.org

    Upstream activity is current, with substantive work in 2025 adding Tegra254/Tegra264 support rather than removal or deprecation.

  2. git.kernel.org

    The driver code explicitly covers modern NVIDIA SoCs including Tegra234 and Tegra241, and 2025 edits show it remains maintained.

  3. nvidia.com

    Jetson Orin modules and developer kits were actively marketed and sold in 2025, indicating ongoing new deployments for Tegra234-class hardware.

  4. nvidia.com

    NVIDIA Grace CPU products remained current in 2025, supporting continued relevance of Tegra241/Grace-related CBB support.

codex reasoning notes (technical)

Real driver, not an asset/helper dir: local shell inspection found platform_driver registration and MODULE_DEVICE_TABLE in tegra194-cbb.c and tegra234-cbb.c. Local `git log` showed sustained upstream attention from 2022-09-15 through 2025-11-14, including new Tegra254/Tegra264 support in July 2025 and no sign of removal discussion. Kernel.org URLs are canonical recall, used to represent the locally verified tree/log pages; NVIDIA product URLs were obtained via web search. This is an SoC-internal error-reporting driver for current Jetson Orin and Grace-family systems, with no natural replacement driver beyond itself, so removal/deprecation is not indicated.