drivers/tty/serial/pmac_zilog.c
Source file repositories/reference/linux-study-clean/drivers/tty/serial/pmac_zilog.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/tty/serial/pmac_zilog.c- Extension
.c- Size
- 48634 bytes
- Lines
- 1974
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/tty.hlinux/tty_flip.hlinux/major.hlinux/string.hlinux/fcntl.hlinux/mm.hlinux/kernel.hlinux/delay.hlinux/init.hlinux/console.hlinux/adb.hlinux/pmu.hlinux/bitops.hlinux/sysrq.hlinux/mutex.hlinux/of_address.hlinux/of_irq.hasm/sections.hlinux/io.hasm/irq.hasm/machdep.hasm/pmac_feature.hasm/macio.hlinux/platform_device.hlinux/serial.hlinux/serial_core.hpmac_zilog.h
Detected Declarations
function pmz_load_zsregsfunction pmz_maybe_update_regsfunction pmz_interrupt_controlfunction pmz_receive_charsfunction pmz_status_handlefunction pmz_transmit_charsfunction pmz_interruptfunction pmz_peek_statusfunction pmz_tx_emptyfunction Controlfunction bitsfunction pmz_stop_txfunction pmz_start_txfunction pmz_stop_rxfunction pmz_enable_msfunction pmz_break_ctlfunction pmz_set_scc_powerfunction pmz_set_scc_powerfunction initializedfunction __pmz_startupfunction pmz_irda_resetfunction pmz_startupfunction pmz_shutdownfunction pmz_convert_to_zsfunction pmz_irda_setupfunction __pmz_set_termiosfunction pmz_set_termiosfunction pmz_release_portfunction pmz_config_portfunction pmz_poll_get_charfunction pmz_poll_put_charfunction uart_add_one_portfunction of_device_is_compatiblefunction pmz_dispose_portfunction pmz_attachfunction pmz_detachfunction pmz_suspendfunction pmz_resumefunction pmz_probefunction for_each_child_of_nodefunction pmz_init_portfunction pmz_probefunction pmz_dispose_portfunction pmz_attachfunction pmz_detachfunction pmz_registerfunction init_pmzfunction exit_pmz
Annotated Snippet
module_init(init_pmz);
module_exit(exit_pmz);
Annotation
- Immediate include surface: `linux/module.h`, `linux/tty.h`, `linux/tty_flip.h`, `linux/major.h`, `linux/string.h`, `linux/fcntl.h`, `linux/mm.h`, `linux/kernel.h`.
- Detected declarations: `function pmz_load_zsregs`, `function pmz_maybe_update_regs`, `function pmz_interrupt_control`, `function pmz_receive_chars`, `function pmz_status_handle`, `function pmz_transmit_chars`, `function pmz_interrupt`, `function pmz_peek_status`, `function pmz_tx_empty`, `function Control`.
- 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.