drivers/usb/gadget/udc/net2280.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/gadget/udc/net2280.c

Extension

.c

Size

102748 bytes

Lines

3883

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/module.h
• linux/pci.h
• linux/dma-mapping.h
• linux/kernel.h
• linux/delay.h
• linux/ioport.h
• linux/slab.h
• linux/errno.h
• linux/init.h
• linux/timer.h
• linux/list.h
• linux/interrupt.h
• linux/moduleparam.h
• linux/device.h
• linux/usb/ch9.h
• linux/usb/gadget.h
• linux/prefetch.h
• linux/io.h
• linux/iopoll.h
• asm/byteorder.h
• asm/irq.h
• linux/unaligned.h
• net2280.h

Detected Declarations

• function enable_pciirqenb
• function net2280_enable
• function handshake
• function ep_reset_228x
• function read
• function ep_reset_338x
• function net2280_disable
• function net2280_free_request
• function write_fifo
• function in
• function out_flush
• function read_fifo
• function fill_dma_desc
• function spin_stop_dma
• function stop_dma
• function start_queue
• function start_dma
• function BIT
• function queue_dma
• function done
• function net2280_queue
• function dma_done
• function scan_dma_completions
• function restart_dma
• function abort_dma
• function nuke
• function net2280_dequeue
• function net2280_set_halt_and_wedge
• function net2280_set_halt
• function net2280_set_wedge
• function net2280_fifo_status
• function net2280_fifo_flush
• function net2280_get_frame
• function net2280_wakeup
• function net2280_set_selfpowered
• function net2280_pullup
• function usb_endpoint_dir_in
• function usb_endpoint_dir_in
• function function_show
• function registers_show
• function queues_show
• function list_for_each_entry
• function set_fifo_mode
• function defect7374_disable_data_eps
• function defect7374_enable_data_eps_zero
• function driver
• function usb_reset_338x
• function usb_reset

Annotated Snippet

static struct pci_driver net2280_pci_driver = {
	.name =		driver_name,
	.id_table =	pci_ids,

	.probe =	net2280_probe,
	.remove =	net2280_remove,
	.shutdown =	net2280_shutdown,

	/* FIXME add power management support */
};

module_pci_driver(net2280_pci_driver);

MODULE_DESCRIPTION(DRIVER_DESC);
MODULE_AUTHOR("David Brownell");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/dma-mapping.h`, `linux/kernel.h`, `linux/delay.h`, `linux/ioport.h`, `linux/slab.h`, `linux/errno.h`.
• Detected declarations: `function enable_pciirqenb`, `function net2280_enable`, `function handshake`, `function ep_reset_228x`, `function read`, `function ep_reset_338x`, `function net2280_disable`, `function net2280_free_request`, `function write_fifo`, `function in`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.