drivers/usb/gadget/legacy/serial.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/gadget/legacy/serial.c

Extension

.c

Size

7982 bytes

Lines

326

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/kernel.h
• linux/device.h
• linux/kstrtox.h
• linux/module.h
• linux/tty.h
• linux/tty_flip.h
• u_serial.h

Detected Declarations

• function enable_set
• function serial_register_ports
• function gs_bind
• function gs_unbind
• function switch_gserial_enable
• function gserial_init
• function gserial_cleanup
• module init gserial_init

Annotated Snippet

module_init(gserial_init);

static void __exit gserial_cleanup(void)
{
	if (enable)
		usb_composite_unregister(&gserial_driver);
}
module_exit(gserial_cleanup);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/device.h`, `linux/kstrtox.h`, `linux/module.h`, `linux/tty.h`, `linux/tty_flip.h`, `u_serial.h`.
• Detected declarations: `function enable_set`, `function serial_register_ports`, `function gs_bind`, `function gs_unbind`, `function switch_gserial_enable`, `function gserial_init`, `function gserial_cleanup`, `module init gserial_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.