drivers/tty/serial/8250/8250_pericom.c

Source file repositories/reference/linux-study-clean/drivers/tty/serial/8250/8250_pericom.c

File Facts

System: Linux kernel
Corpus path: drivers/tty/serial/8250/8250_pericom.c
Extension: .c
Size: 7722 bytes
Lines: 215
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.
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/bits.h
linux/module.h
linux/overflow.h
linux/pci.h
8250.h

Detected Declarations

struct pericom8250
function pericom_do_set_divisor
function pericom8250_probe
function pericom8250_remove

Annotated Snippet

static struct pci_driver pericom8250_pci_driver = {
	.name           = "8250_pericom",
	.id_table       = pericom8250_pci_ids,
	.probe          = pericom8250_probe,
	.remove         = pericom8250_remove,
};
module_pci_driver(pericom8250_pci_driver);

MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("Pericom UART driver");

Annotation

Immediate include surface: `linux/bits.h`, `linux/module.h`, `linux/overflow.h`, `linux/pci.h`, `8250.h`.
Detected declarations: `struct pericom8250`, `function pericom_do_set_divisor`, `function pericom8250_probe`, `function pericom8250_remove`.
Atlas domain: Driver Families / drivers/tty.
Implementation status: pattern implementation candidate.

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.