drivers/scsi/qedi/qedi_dbg.h
Source file repositories/reference/linux-study-clean/drivers/scsi/qedi/qedi_dbg.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/qedi/qedi_dbg.h- Extension
.h- Size
- 4013 bytes
- Lines
- 127
- Domain
- Driver Families
- Bucket
- drivers/scsi
- Inferred role
- Driver Families: operation-table or driver-model contract
- Status
- pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.hlinux/kernel.hlinux/compiler.hlinux/string.hlinux/pci.hlinux/delay.hscsi/scsi_transport.hscsi/scsi_transport_iscsi.hlinux/fs.hlinux/qed/common_hsi.hlinux/qed/qed_if.h
Detected Declarations
struct qedi_dbg_ctxstruct qedi_list_of_funcsstruct qedi_debugfs_ops
Annotated Snippet
const struct file_operations *fops);
void qedi_dbg_host_exit(struct qedi_dbg_ctx *qedi);
void qedi_dbg_init(char *drv_name);
void qedi_dbg_exit(void);
#endif /* _QEDI_DBG_H_ */Annotation
- Immediate include surface: `linux/types.h`, `linux/kernel.h`, `linux/compiler.h`, `linux/string.h`, `linux/pci.h`, `linux/delay.h`, `scsi/scsi_transport.h`, `scsi/scsi_transport_iscsi.h`.
- Detected declarations: `struct qedi_dbg_ctx`, `struct qedi_list_of_funcs`, `struct qedi_debugfs_ops`.
- Atlas domain: Driver Families / drivers/scsi.
- Implementation status: pattern 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.