drivers/scsi/mpi3mr/mpi/mpi30_sas.h
Source file repositories/reference/linux-study-clean/drivers/scsi/mpi3mr/mpi/mpi30_sas.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/mpi3mr/mpi/mpi30_sas.h- Extension
.h- Size
- 1963 bytes
- Lines
- 48
- Domain
- Driver Families
- Bucket
- drivers/scsi
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct mpi3_smp_passthrough_requeststruct mpi3_smp_passthrough_reply
Annotated Snippet
struct mpi3_smp_passthrough_request {
__le16 host_tag;
u8 ioc_use_only02;
u8 function;
__le16 ioc_use_only04;
u8 ioc_use_only06;
u8 msg_flags;
__le16 change_count;
u8 reserved0a;
u8 io_unit_port;
__le32 reserved0c[3];
__le64 sas_address;
struct mpi3_sge_common request_sge;
struct mpi3_sge_common response_sge;
};
struct mpi3_smp_passthrough_reply {
__le16 host_tag;
u8 ioc_use_only02;
u8 function;
__le16 ioc_use_only04;
u8 ioc_use_only06;
u8 msg_flags;
__le16 ioc_use_only08;
__le16 ioc_status;
__le32 ioc_log_info;
__le16 response_data_length;
__le16 reserved12;
};
#endif
Annotation
- Detected declarations: `struct mpi3_smp_passthrough_request`, `struct mpi3_smp_passthrough_reply`.
- Atlas domain: Driver Families / drivers/scsi.
- Implementation status: source implementation candidate.
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.