drivers/usb/atm/xusbatm.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/atm/xusbatm.c

Extension

.c

Size

7033 bytes

Lines

217

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

Dependency Surface

• linux/module.h
• linux/etherdevice.h
• usbatm.h

Detected Declarations

• function xusbatm_capture_intf
• function xusbatm_release_intf
• function xusbatm_bind
• function xusbatm_unbind
• function xusbatm_atm_start
• function xusbatm_usb_probe
• function xusbatm_init
• function xusbatm_exit
• module init xusbatm_init

Annotated Snippet

module_init(xusbatm_init);

static void __exit xusbatm_exit(void)
{
	usb_deregister(&xusbatm_usb_driver);
}
module_exit(xusbatm_exit);

MODULE_AUTHOR("Roman Kagan, Duncan Sands");
MODULE_DESCRIPTION("Driver for USB ADSL modems initialized in userspace");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/etherdevice.h`, `usbatm.h`.
• Detected declarations: `function xusbatm_capture_intf`, `function xusbatm_release_intf`, `function xusbatm_bind`, `function xusbatm_unbind`, `function xusbatm_atm_start`, `function xusbatm_usb_probe`, `function xusbatm_init`, `function xusbatm_exit`, `module init xusbatm_init`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: integration 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.