drivers/usb/atm/usbatm.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/atm/usbatm.c

Extension

.c

Size

35501 bytes

Lines

1330

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• usbatm.h
• linux/uaccess.h
• linux/crc32.h
• linux/errno.h
• linux/init.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/moduleparam.h
• linux/netdevice.h
• linux/proc_fs.h
• linux/sched/signal.h
• linux/signal.h
• linux/slab.h
• linux/stat.h
• linux/timer.h
• linux/wait.h
• linux/kthread.h
• linux/ratelimit.h

Detected Declarations

• struct usbatm_vcc_data
• struct usbatm_control
• function usbatm_pdu_length
• function usbatm_pop
• function usbatm_submit_urb
• function usbatm_complete
• function usbatm_extract_one_cell
• function usbatm_extract_cells
• function usbatm_write_cells
• function usbatm_rx_process
• function usbatm_tx_process
• function usbatm_cancel_send
• function usbatm_atm_send
• function usbatm_destroy_instance
• function usbatm_get_instance
• function usbatm_put_instance
• function usbatm_atm_dev_close
• function usbatm_atm_proc_read
• function usbatm_atm_open
• function usbatm_atm_close
• function usbatm_atm_ioctl
• function usbatm_atm_init
• function usbatm_do_heavy_init
• function usbatm_heavy_init
• function usbatm_tasklet_schedule
• function usbatm_init_channel
• function usbatm_usb_probe
• function usbatm_usb_disconnect
• function usbatm_usb_init
• function usbatm_usb_exit
• function usbatm_print_packet
• module init usbatm_usb_init
• export usbatm_usb_probe
• export usbatm_usb_disconnect

Annotated Snippet

module_init(usbatm_usb_init);

static void __exit usbatm_usb_exit(void)
{
}
module_exit(usbatm_usb_exit);

MODULE_AUTHOR(DRIVER_AUTHOR);
MODULE_DESCRIPTION(DRIVER_DESC);
MODULE_LICENSE("GPL");

/************
**  debug  **
************/

#ifdef VERBOSE_DEBUG
static int usbatm_print_packet(struct usbatm_data *instance,
			       const unsigned char *data, int len)
{
	unsigned char buffer[256];
	int i = 0, j = 0;

	for (i = 0; i < len;) {
		buffer[0] = '\0';
		sprintf(buffer, "%.3d :", i);
		for (j = 0; (j < 16) && (i < len); j++, i++)
			sprintf(buffer, "%s %2.2x", buffer, data[i]);
		dev_dbg(&instance->usb_intf->dev, "%s", buffer);
	}
	return i;
}
#endif

Annotation

• Immediate include surface: `usbatm.h`, `linux/uaccess.h`, `linux/crc32.h`, `linux/errno.h`, `linux/init.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`.
• Detected declarations: `struct usbatm_vcc_data`, `struct usbatm_control`, `function usbatm_pdu_length`, `function usbatm_pop`, `function usbatm_submit_urb`, `function usbatm_complete`, `function usbatm_extract_one_cell`, `function usbatm_extract_cells`, `function usbatm_write_cells`, `function usbatm_rx_process`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.