drivers/scsi/hisi_sas/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/scsi/hisi_sas/Kconfig

Extension

[no extension]

Size

689 bytes

Lines

27

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
config SCSI_HISI_SAS
	tristate "HiSilicon SAS"
	depends on HAS_IOMEM
	depends on ARM64 || COMPILE_TEST
	select SCSI_SAS_LIBSAS
	select BLK_DEV_INTEGRITY
	depends on ATA
	select SATA_HOST
	help
		This driver supports HiSilicon's SAS HBA, including support based
		on platform device

config SCSI_HISI_SAS_PCI
	tristate "HiSilicon SAS on PCI bus"
	depends on SCSI_HISI_SAS
	depends on PCI
	depends on ACPI
	help
		This driver supports HiSilicon's SAS HBA based on PCI device

config SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE
	bool "HiSilicon SAS debugging default enable"
	depends on SCSI_HISI_SAS
	help
		Set Y to default enable DEBUGFS for SCSI_HISI_SAS

Annotation

• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.