drivers/tty/serial/8250/8250_pci1xxxx.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/8250/8250_pci1xxxx.c

Extension

.c

Size

24672 bytes

Lines

888

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/array_size.h
• linux/bitfield.h
• linux/bits.h
• linux/circ_buf.h
• linux/device.h
• linux/errno.h
• linux/gfp_types.h
• linux/io.h
• linux/iopoll.h
• linux/minmax.h
• linux/module.h
• linux/mutex.h
• linux/overflow.h
• linux/pci.h
• linux/pm.h
• linux/serial_core.h
• linux/serial_reg.h
• linux/serial_8250.h
• linux/spinlock.h
• linux/string.h
• linux/time.h
• linux/tty.h
• linux/tty_flip.h
• linux/types.h
• linux/units.h
• asm/byteorder.h
• 8250.h
• 8250_pcilib.h

Detected Declarations

• struct pci1xxxx_8250
• function pci1xxxx_set_sys_lock
• function pci1xxxx_acquire_sys_lock
• function pci1xxxx_release_sys_lock
• function pci1xxxx_get_num_ports
• function pci1xxxx_get_divisor
• function pci1xxxx_set_divisor
• function pci1xxxx_set_mctrl
• function pci1xxxx_rs485_config
• function pci1xxxx_read_burst_status
• function pci1xxxx_process_read_data
• function pci1xxxx_rx_burst
• function pci1xxxx_process_write_data
• function pci1xxxx_tx_burst
• function pci1xxxx_handle_irq
• function pci1xxxx_port_suspend
• function pci1xxxx_port_resume
• function pci1xxxx_suspend
• function pci1xxxx_resume
• function pci1xxxx_setup
• function pci1xxxx_get_max_port
• function pci1xxxx_logical_to_physical_port_translate
• function pci1xxxx_get_device_revision
• function pci1xxxx_serial_probe
• function pci1xxxx_serial_remove

Annotated Snippet

static struct pci_driver pci1xxxx_pci_driver = {
	.name = "pci1xxxx serial",
	.probe = pci1xxxx_serial_probe,
	.remove = pci1xxxx_serial_remove,
	.driver = {
		.pm     = pm_sleep_ptr(&pci1xxxx_pm_ops),
	},
	.id_table = pci1xxxx_pci_tbl,
};
module_pci_driver(pci1xxxx_pci_driver);

static_assert((ARRAY_SIZE(logical_to_physical_port_idx) == PCI_SUBDEVICE_ID_EFAR_PCI1XXXX_1p3 + 1));

MODULE_IMPORT_NS("SERIAL_8250_PCI");
MODULE_DESCRIPTION("Microchip Technology Inc. PCIe to UART module");
MODULE_AUTHOR("Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>");
MODULE_AUTHOR("Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/array_size.h`, `linux/bitfield.h`, `linux/bits.h`, `linux/circ_buf.h`, `linux/device.h`, `linux/errno.h`, `linux/gfp_types.h`, `linux/io.h`.
• Detected declarations: `struct pci1xxxx_8250`, `function pci1xxxx_set_sys_lock`, `function pci1xxxx_acquire_sys_lock`, `function pci1xxxx_release_sys_lock`, `function pci1xxxx_get_num_ports`, `function pci1xxxx_get_divisor`, `function pci1xxxx_set_divisor`, `function pci1xxxx_set_mctrl`, `function pci1xxxx_rs485_config`, `function pci1xxxx_read_burst_status`.
• 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.