drivers/tty/serial/sc16is7xx.c
Source file repositories/reference/linux-study-clean/drivers/tty/serial/sc16is7xx.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/tty/serial/sc16is7xx.c- Extension
.c- Size
- 51891 bytes
- Lines
- 1769
- Domain
- Driver Families
- Bucket
- drivers/tty
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- 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/bits.hlinux/cleanup.hlinux/clk.hlinux/delay.hlinux/device.hlinux/export.hlinux/gpio/consumer.hlinux/gpio/driver.hlinux/idr.hlinux/kthread.hlinux/mod_devicetable.hlinux/module.hlinux/property.hlinux/regmap.hlinux/sched.hlinux/serial_core.hlinux/serial.hlinux/string.hlinux/tty.hlinux/tty_flip.hlinux/uaccess.hlinux/units.hsc16is7xx.h
Detected Declarations
struct sc16is7xx_one_configstruct sc16is7xx_onestruct sc16is7xx_portfunction sc16is7xx_port_readfunction sc16is7xx_port_writefunction sc16is7xx_fifo_readfunction sc16is7xx_fifo_writefunction sc16is7xx_port_updatefunction sc16is7xx_powerfunction Registerfunction sc16is7xx_regs_unlockfunction sc16is7xx_ier_clearfunction sc16is7xx_ier_setfunction sc16is7xx_stop_txfunction sc16is7xx_stop_rxfunction sc16is7xx_regmap_volatilefunction sc16is7xx_regmap_preciousfunction sc16is7xx_regmap_noincfunction generatorfunction sc16is7xx_handle_rxfunction sc16is7xx_handle_txfunction sc16is7xx_get_hwmctrlfunction sc16is7xx_update_mlinesfunction sc16is7xx_port_irqfunction sc16is7xx_irqfunction sc16is7xx_poll_procfunction sc16is7xx_tx_procfunction sc16is7xx_reconf_rs485function sc16is7xx_reg_procfunction sc16is7xx_ms_procfunction sc16is7xx_enable_msfunction sc16is7xx_start_txfunction sc16is7xx_throttlefunction sc16is7xx_unthrottlefunction sc16is7xx_tx_emptyfunction sc16is7xx_get_mctrlfunction sc16is7xx_set_mctrlfunction sc16is7xx_break_ctlfunction sc16is7xx_set_termiosfunction sc16is7xx_config_rs485function sc16is7xx_startupfunction sc16is7xx_shutdownfunction sc16is7xx_request_portfunction sc16is7xx_config_portfunction sc16is7xx_verify_portfunction sc16is7xx_pmfunction sc16is7xx_null_voidfunction sc16is7xx_gpio_get
Annotated Snippet
module_init(sc16is7xx_init);
static void __exit sc16is7xx_exit(void)
{
uart_unregister_driver(&sc16is7xx_uart);
}
module_exit(sc16is7xx_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Jon Ringle <jringle@gridpoint.com>");
MODULE_DESCRIPTION(KBUILD_MODNAME " tty serial core driver");
Annotation
- Immediate include surface: `linux/bits.h`, `linux/cleanup.h`, `linux/clk.h`, `linux/delay.h`, `linux/device.h`, `linux/export.h`, `linux/gpio/consumer.h`, `linux/gpio/driver.h`.
- Detected declarations: `struct sc16is7xx_one_config`, `struct sc16is7xx_one`, `struct sc16is7xx_port`, `function sc16is7xx_port_read`, `function sc16is7xx_port_write`, `function sc16is7xx_fifo_read`, `function sc16is7xx_fifo_write`, `function sc16is7xx_port_update`, `function sc16is7xx_power`, `function Register`.
- Atlas domain: Driver Families / drivers/tty.
- Implementation status: integration 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.