drivers/scsi/qla4xxx/ql4_bsg.h

File Facts

System

Linux kernel

Corpus path

drivers/scsi/qla4xxx/ql4_bsg.h

Extension

.h

Size

950 bytes

Lines

32

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.

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

#ifndef __QL4_BSG_H
#define __QL4_BSG_H

/* BSG Vendor specific commands */
#define QLISCSI_VND_READ_FLASH		1
#define QLISCSI_VND_UPDATE_FLASH	2
#define QLISCSI_VND_GET_ACB_STATE	3
#define QLISCSI_VND_READ_NVRAM		4
#define QLISCSI_VND_UPDATE_NVRAM	5
#define QLISCSI_VND_RESTORE_DEFAULTS	6
#define QLISCSI_VND_GET_ACB		7
#define QLISCSI_VND_DIAG_TEST		8

/* QLISCSI_VND_DIAG_CMD sub code */
#define QL_DIAG_CMD_TEST_DDR_SIZE	0x2
#define QL_DIAG_CMD_TEST_DDR_RW		0x3
#define QL_DIAG_CMD_TEST_ONCHIP_MEM_RW	0x4
#define QL_DIAG_CMD_TEST_NVRAM		0x5	/* Only ISP4XXX */
#define QL_DIAG_CMD_TEST_FLASH_ROM	0x6
#define QL_DIAG_CMD_TEST_INT_LOOPBACK	0x7
#define QL_DIAG_CMD_TEST_EXT_LOOPBACK	0x8
#define QL_DIAG_CMD_TEST_DMA_XFER	0x9	/* Only ISP4XXX */
#define QL_DIAG_CMD_SELF_DDR_RW		0xC
#define QL_DIAG_CMD_SELF_ONCHIP_MEM_RW	0xD

#endif

Annotation

• 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.