drivers/tty/serial/8250/8250_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/8250/8250_pci.c

Extension

.c

Size

163081 bytes

Lines

6325

Domain

Driver Families

Bucket

drivers/tty

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/string.h
• linux/kernel.h
• linux/math.h
• linux/slab.h
• linux/delay.h
• linux/tty.h
• linux/serial_reg.h
• linux/serial_core.h
• linux/8250_pci.h
• linux/bitops.h
• linux/bitfield.h
• asm/byteorder.h
• asm/io.h
• 8250.h
• 8250_pcilib.h

Detected Declarations

• struct pci_serial_quirk
• struct f815xxa_data
• struct serial_private
• enum pci_board_num_t
• function moan_device
• function setup_port
• function addidata_apci7800_setup
• function afavlab_setup
• function UARTs
• function pci_hp_diva_setup
• function pci_inteli960ni_init
• function pci_plx9050_init
• function pci_plx9050_exit
• function pci_ni8420_exit
• function pci_ni8430_exit
• function sbs_setup
• function sbs_init
• function sbs_exit
• function pci_siig10x_init
• function pci_siig20x_init
• function pci_siig_init
• function pci_siig_setup
• function pci_timedia_probe
• function pci_timedia_init
• function pci_timedia_setup
• function titan_400l_800l_setup
• function pci_xircom_init
• function pci_ni8420_init
• function pci_ni8430_init
• function pci_ni8430_setup
• function pci_netmos_9900_setup
• function pci_netmos_9900_numports
• function pci_netmos_init
• function pci_ite887x_init
• function pci_ite887x_exit
• function pci_oxsemi_tornado_p
• function pci_oxsemi_tornado_init
• function inclusive
• function register
• function prescaler
• function pci_oxsemi_tornado_setup
• function pci_quatech_rqopr
• function pci_quatech_wqopr
• function pci_quatech_rqmcr
• function pci_quatech_wqmcr
• function pci_quatech_has_qmcr
• function pci_quatech_test
• function pci_quatech_clock

Annotated Snippet

static struct pci_driver serial_pci_driver = {
	.name		= "serial",
	.probe		= pciserial_init_one,
	.remove		= pciserial_remove_one,
	.driver         = {
		.pm     = &pciserial_pm_ops,
	},
	.id_table	= serial_pci_tbl,
	.err_handler	= &serial8250_err_handler,
};

module_pci_driver(serial_pci_driver);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Generic 8250/16x50 PCI serial probe module");
MODULE_DEVICE_TABLE(pci, serial_pci_tbl);
MODULE_IMPORT_NS("SERIAL_8250_PCI");

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/string.h`, `linux/kernel.h`, `linux/math.h`, `linux/slab.h`, `linux/delay.h`, `linux/tty.h`.
• Detected declarations: `struct pci_serial_quirk`, `struct f815xxa_data`, `struct serial_private`, `enum pci_board_num_t`, `function moan_device`, `function setup_port`, `function addidata_apci7800_setup`, `function afavlab_setup`, `function UARTs`, `function pci_hp_diva_setup`.
• Atlas domain: Driver Families / drivers/tty.
• 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.