drivers/scsi/isci

Intel C600/C602 Series Chipset SAS Storage Controllers

The integrated SAS/SATA storage controller built into Intel's C600-series server chipsets (Patsburg), launched in early 2012 alongside Xeon E5 platforms and used in many Sandy Bridge/Ivy Bridge-EP servers and workstations through about 2015. It drives the on-chipset SAS host hardware that those boards exposed to disks and tape drives.

keep-annotate conf=0.78 last_sold=2015 deploy=low replacement=none subsystem=scsi category=storage-scsi-ata
78%

recommendation

Worth keeping but flagging as legacy because the underlying C600/C602 chipsets were discontinued by Intel and have not been sold new since around 2015, yet a meaningful installed base of Xeon E5-era servers still depends on this code. Upstream activity in 2024 and 2025 on linux-scsi shows the driver is still being maintained rather than abandoned, and there is no generic replacement since this targets a specific integrated SAS block.

repository signals

30 files
22,953 source lines
36 commits, 5y
+97 / −249 lines added / removed, 5y
21 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 36 total · active in 23/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 2 commits · +8 −8 2021-06: 1 commit · +1 −0 2021-07: 0 commits · +0 −0 2021-08: 1 commit · +2 −2 2021-09: 0 commits · +0 −0 2021-10: 2 commits · +5 −7 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 4 commits · +22 −51 2022-03: 1 commit · +3 −3 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +1 −1 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 1 commit · +1 −1 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 1 commit · +1 −1 2023-07: 0 commits · +0 −0 2023-08: 6 commits · +5 −10 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 1 commit · +3 −8 2023-12: 0 commits · +0 −0 2024-01: 2 commits · +2 −2 2024-02: 0 commits · +0 −0 2024-03: 2 commits · +8 −21 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +1 −0 2024-07: 1 commit · +1 −5 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +0 −46 2025-01: 1 commit · +1 −1 2025-02: 0 commits · +0 −0 2025-03: 1 commit · +7 −14 2025-04: 1 commit · +10 −10 2025-05: 2 commits · +7 −52 2025-06: 1 commit · +1 −1 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +1 −1 2025-09: 1 commit · +6 −4 2025-10: 0 commits · +0 −0 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. lore.kernel.org

    The driver still receives upstream touch-ups in 2025, indicating it is not abandoned.

  2. lore.kernel.org

    The driver was included in 2024 SCSI tree maintenance work, showing continued build/metadata upkeep.

  3. cateee.net

    CONFIG_SCSI_ISCI is the Intel C600 Series Chipset SAS Controller driver and matches C60x-era PCI IDs.

  4. intel.com

    Intel C602, part of the C600 Series Chipsets family targeted by isci, is marked Discontinued and launched in Q1 2012.

  5. intel.com

    Intel lists the C602 ordering page as retired/discontinued, supporting that new hardware sales ended long ago.

codex reasoning notes (technical)

Lore evidence first: `lore_activity` on drivers/scsi/isci/init.c returned 32 linux-scsi hits in 5y, including 2025 and 2024 patch traffic at the cited lore URLs; this argues against deprecate/remove. A `lore_regex` subject scan for isci timed out, so no positive removal-thread evidence was obtained. Hardware identity came from local tree Kconfig plus web-obtained LKDDb URL. Deployment judgment is based on web-obtained Intel ARK pages showing the C600/C602 family is a 2012 server chipset and discontinued/retired; that implies legacy installed-base use only, with low but nonzero deployments today. No natural replacement driver exists because isci is for this specific integrated SAS block rather than a generic interface.