drivers/scsi/hisi_sas/hisi_sas_main.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/hisi_sas/hisi_sas_main.c

Extension

.c

Size

71190 bytes

Lines

2703

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• hisi_sas.h

Detected Declarations

• struct hisi_sas_internal_abort_data
• function hisi_sas_get_ata_protocol_from_tf
• function hisi_sas_get_ata_protocol
• function hisi_sas_sata_done
• function hisi_sas_get_prog_phy_linkrate_mask
• function hisi_sas_stop_phys
• function hisi_sas_slot_index_clear
• function hisi_sas_slot_index_free
• function hisi_sas_slot_index_set
• function hisi_sas_slot_index_alloc
• function hisi_sas_slot_task_free
• function hisi_sas_task_prep_smp
• function hisi_sas_task_prep_ssp
• function hisi_sas_task_prep_ata
• function hisi_sas_task_prep_abort
• function hisi_sas_dma_unmap
• function hisi_sas_dma_map
• function hisi_sas_dif_dma_unmap
• function hisi_sas_dif_dma_map
• function hisi_sas_task_deliver
• function hisi_sas_queue_command
• function hisi_sas_bytes_dmaed
• function hisi_sas_sync_poll_cq
• function hisi_sas_queue_is_poll
• function hisi_sas_sync_cq
• function hisi_sas_sync_poll_cqs
• function hisi_sas_sync_cqs
• function hisi_sas_tmf_aborted
• function hisi_sas_init_device
• function sas_probe_sata
• function hisi_sas_sdev_init
• function hisi_sas_dev_found
• function hisi_sas_sdev_configure
• function hisi_sas_scan_start
• function hisi_sas_scan_finished
• function hisi_sas_phyup_work_common
• function hisi_sas_phyup_work
• function hisi_sas_linkreset_work
• function hisi_sas_phyup_pm_work
• function hisi_sas_notify_phy_event
• function hisi_sas_wait_phyup_timedout
• function hisi_sas_phy_oob_ready
• function hisi_sas_phy_init
• function hisi_sas_phy_enable
• function hisi_sas_port_notify_formed
• function hisi_sas_do_release_task
• function hisi_sas_release_task
• function hisi_sas_release_tasks

Annotated Snippet

module_init(hisi_sas_init);
module_exit(hisi_sas_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("John Garry <john.garry@huawei.com>");
MODULE_DESCRIPTION("HISILICON SAS controller driver");
MODULE_ALIAS("platform:" DRV_NAME);

Annotation

• Immediate include surface: `hisi_sas.h`.
• Detected declarations: `struct hisi_sas_internal_abort_data`, `function hisi_sas_get_ata_protocol_from_tf`, `function hisi_sas_get_ata_protocol`, `function hisi_sas_sata_done`, `function hisi_sas_get_prog_phy_linkrate_mask`, `function hisi_sas_stop_phys`, `function hisi_sas_slot_index_clear`, `function hisi_sas_slot_index_free`, `function hisi_sas_slot_index_set`, `function hisi_sas_slot_index_alloc`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.