drivers/usb/gadget/udc/pch_udc.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/gadget/udc/pch_udc.c

Extension

.c

Size

88067 bytes

Lines

3163

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/kernel.h
• linux/module.h
• linux/pci.h
• linux/delay.h
• linux/errno.h
• linux/gpio/consumer.h
• linux/gpio/machine.h
• linux/list.h
• linux/interrupt.h
• linux/usb/ch9.h
• linux/usb/gadget.h
• linux/irq.h

Detected Declarations

• struct pch_udc_data_dma_desc
• struct pch_udc_stp_dma_desc
• struct pch_udc_cfg_data
• struct pch_udc_ep
• struct pch_vbus_gpio_data
• struct pch_udc_dev
• struct pch_udc_request
• function pch_udc_readl
• function pch_udc_writel
• function pch_udc_bit_set
• function pch_udc_bit_clr
• function pch_udc_ep_readl
• function pch_udc_ep_writel
• function pch_udc_ep_bit_set
• function pch_udc_ep_bit_clr
• function pch_udc_csr_busy
• function pch_udc_write_csr
• function pch_udc_read_csr
• function pch_udc_rmt_wakeup
• function pch_udc_get_frame
• function pch_udc_clear_selfpowered
• function pch_udc_set_selfpowered
• function pch_udc_set_disconnect
• function pch_udc_clear_disconnect
• function pch_udc_reconnect
• function pch_udc_vbus_session
• function pch_udc_ep_set_stall
• function pch_udc_ep_clear_stall
• function pch_udc_ep_set_trfr_type
• function pch_udc_ep_set_bufsz
• function pch_udc_ep_set_maxpkt
• function pch_udc_ep_set_subptr
• function pch_udc_ep_set_ddptr
• function pch_udc_ep_set_pd
• function pch_udc_ep_set_rrdy
• function pch_udc_ep_clear_rrdy
• function pch_udc_set_dma
• function pch_udc_clear_dma
• function pch_udc_set_csr_done
• function pch_udc_disable_interrupts
• function pch_udc_enable_interrupts
• function pch_udc_disable_ep_interrupts
• function pch_udc_enable_ep_interrupts
• function pch_udc_read_device_interrupts
• function pch_udc_write_device_interrupts
• function pch_udc_read_ep_interrupts
• function pch_udc_write_ep_interrupts
• function pch_udc_read_device_status

Annotated Snippet

static struct pci_driver pch_udc_driver = {
	.name =	KBUILD_MODNAME,
	.id_table =	pch_udc_pcidev_id,
	.probe =	pch_udc_probe,
	.remove =	pch_udc_remove,
	.shutdown =	pch_udc_shutdown,
	.driver = {
		.pm = &pch_udc_pm,
	},
};

module_pci_driver(pch_udc_driver);

MODULE_DESCRIPTION("Intel EG20T USB Device Controller");
MODULE_AUTHOR("LAPIS Semiconductor, <tomoya-linux@dsn.lapis-semi.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/delay.h`, `linux/errno.h`, `linux/gpio/consumer.h`, `linux/gpio/machine.h`, `linux/list.h`.
• Detected declarations: `struct pch_udc_data_dma_desc`, `struct pch_udc_stp_dma_desc`, `struct pch_udc_cfg_data`, `struct pch_udc_ep`, `struct pch_vbus_gpio_data`, `struct pch_udc_dev`, `struct pch_udc_request`, `function pch_udc_readl`, `function pch_udc_writel`, `function pch_udc_bit_set`.
• 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.