drivers/usb/gadget/legacy/raw_gadget.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/gadget/legacy/raw_gadget.c

Extension

.c

Size

33960 bytes

Lines

1377

Domain

Driver Families

Bucket

drivers/usb

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.
• 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

• linux/compiler.h
• linux/ctype.h
• linux/debugfs.h
• linux/delay.h
• linux/idr.h
• linux/kref.h
• linux/miscdevice.h
• linux/module.h
• linux/semaphore.h
• linux/sched.h
• linux/slab.h
• linux/uaccess.h
• linux/wait.h
• linux/usb.h
• linux/usb/ch9.h
• linux/usb/ch11.h
• linux/usb/gadget.h
• linux/usb/composite.h
• uapi/linux/usb/raw_gadget.h

Detected Declarations

• struct raw_event_queue
• struct raw_dev
• struct raw_ep
• struct raw_dev
• enum ep_state
• enum dev_state
• function raw_event_queue_init
• function raw_event_queue_add
• function down_interruptible
• function raw_event_queue_destroy
• function dev_free
• function raw_queue_event
• function gadget_ep0_complete
• function get_ep_addr
• function gadget_bind
• function gadget_unbind
• function gadget_setup
• function gadget_disconnect
• function gadget_suspend
• function gadget_resume
• function gadget_reset
• function raw_open
• function raw_release
• function raw_ioctl_init
• function raw_ioctl_run
• function raw_ioctl_event_fetch
• function raw_process_ep0_io
• function raw_ioctl_ep0_write
• function raw_ioctl_ep0_read
• function raw_ioctl_ep0_stall
• function raw_ioctl_ep_enable
• function raw_ioctl_ep_disable
• function raw_ioctl_ep_set_clear_halt_wedge
• function gadget_ep_complete
• function raw_process_ep_io
• function raw_ioctl_ep_write
• function raw_ioctl_ep_read
• function raw_ioctl_configure
• function raw_ioctl_vbus_draw
• function fill_ep_caps
• function fill_ep_limits
• function raw_ioctl_eps_info
• function raw_ioctl

Annotated Snippet

static const struct file_operations raw_fops = {
	.open =			raw_open,
	.unlocked_ioctl =	raw_ioctl,
	.compat_ioctl =		raw_ioctl,
	.release =		raw_release,
};

static struct miscdevice raw_misc_device = {
	.minor = MISC_DYNAMIC_MINOR,
	.name = DRIVER_NAME,
	.fops = &raw_fops,
};

module_misc_device(raw_misc_device);

Annotation

• Immediate include surface: `linux/compiler.h`, `linux/ctype.h`, `linux/debugfs.h`, `linux/delay.h`, `linux/idr.h`, `linux/kref.h`, `linux/miscdevice.h`, `linux/module.h`.
• Detected declarations: `struct raw_event_queue`, `struct raw_dev`, `struct raw_ep`, `struct raw_dev`, `enum ep_state`, `enum dev_state`, `function raw_event_queue_init`, `function raw_event_queue_add`, `function down_interruptible`, `function raw_event_queue_destroy`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: pattern 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.