drivers/tty/serial/8250/8250_exar.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/8250/8250_exar.c

Extension

.c

Size

52666 bytes

Lines

1748

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.
• 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/bitfield.h
• linux/bits.h
• linux/delay.h
• linux/device.h
• linux/dmi.h
• linux/eeprom_93cx6.h
• linux/interrupt.h
• linux/io.h
• linux/math.h
• linux/module.h
• linux/pci.h
• linux/platform_device.h
• linux/pm.h
• linux/property.h
• linux/string.h
• linux/types.h
• linux/serial_8250.h
• linux/serial_core.h
• linux/serial_reg.h
• asm/byteorder.h
• 8250.h
• 8250_pcilib.h

Detected Declarations

• struct exar8250
• struct exar8250_platform
• struct exar8250_board
• struct exar8250
• enum cti_port_type
• function exar_write_reg
• function exar_read_reg
• function exar_eeprom_93cx6_reg_read
• function exar_eeprom_93cx6_reg_write
• function exar_eeprom_init
• function exar_mpio_config_output
• function _exar_mpio_set
• function exar_mpio_set_low
• function exar_mpio_set_high
• function generic_rs485_config
• function exar_pm
• function register
• function xr17v35x_set_divisor
• function xr17v35x_startup
• function exar_shutdown
• function default_setup
• function pci_fastcom335_setup
• function cti_tristate_disable
• function cti_plx_int_enable
• function cti_read_osc_freq
• function cti_get_port_type_xr17c15x_xr17v25x
• function cti_get_port_type_fpga
• function cti_get_port_type_xr17v35x
• function cti_rs485_config_mpio_tristate
• function cti_board_init_osc_freq
• function cti_port_setup_common
• function cti_board_init_fpga
• function cti_port_setup_fpga
• function cti_board_init_xr17v35x
• function cti_port_setup_xr17v35x
• function cti_board_init_xr17v25x
• function cti_port_setup_xr17v25x
• function cti_board_init_xr17c15x
• function cti_port_setup_xr17c15x
• function pci_xr17c154_setup
• function setup_gpio
• function __xr17v35x_unregister_gpio
• function xr17v35x_register_gpio
• function xr17v35x_unregister_gpio
• function sealevel_rs485_config
• function iot2040_rs485_config
• function iot2040_register_gpio
• function pci_xr17v35x_setup

Annotated Snippet

static struct pci_driver exar_pci_driver = {
	.name		= "exar_serial",
	.probe		= exar_pci_probe,
	.remove		= exar_pci_remove,
	.driver         = {
		.pm     = pm_sleep_ptr(&exar_pci_pm),
	},
	.id_table	= exar_pci_tbl,
};
module_pci_driver(exar_pci_driver);

MODULE_IMPORT_NS("SERIAL_8250_PCI");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Exar Serial Driver");
MODULE_AUTHOR("Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>");

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/bits.h`, `linux/delay.h`, `linux/device.h`, `linux/dmi.h`, `linux/eeprom_93cx6.h`, `linux/interrupt.h`, `linux/io.h`.
• Detected declarations: `struct exar8250`, `struct exar8250_platform`, `struct exar8250_board`, `struct exar8250`, `enum cti_port_type`, `function exar_write_reg`, `function exar_read_reg`, `function exar_eeprom_93cx6_reg_read`, `function exar_eeprom_93cx6_reg_write`, `function exar_eeprom_init`.
• Atlas domain: Driver Families / drivers/tty.
• Implementation status: pattern implementation candidate.
• 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.