drivers/usb/storage/usb.h

File Facts

System

Linux kernel

Corpus path

drivers/usb/storage/usb.h

Extension

.h

Size

7175 bytes

Lines

211

Domain

Driver Families

Bucket

drivers/usb

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/usb.h
• linux/usb_usual.h
• linux/blkdev.h
• linux/completion.h
• linux/mutex.h
• linux/workqueue.h
• scsi/scsi_host.h

Detected Declarations

• struct us_data
• struct scsi_cmnd
• struct us_unusual_dev
• struct us_data

Annotated Snippet

module_init(__driver##_init); \
static void __exit __driver##_exit(void) \
{ \
	usb_deregister(&(__driver)); \
} \
module_exit(__driver##_exit)

#endif

Annotation

• Immediate include surface: `linux/usb.h`, `linux/usb_usual.h`, `linux/blkdev.h`, `linux/completion.h`, `linux/mutex.h`, `linux/workqueue.h`, `scsi/scsi_host.h`.
• Detected declarations: `struct us_data`, `struct scsi_cmnd`, `struct us_unusual_dev`, `struct us_data`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.