drivers/ipack/devices/ipoctal.c

File Facts

System

Linux kernel

Corpus path

drivers/ipack/devices/ipoctal.c

Extension

.c

Size

19485 bytes

Lines

773

Domain

Driver Families

Bucket

drivers/ipack

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/device.h
• linux/module.h
• linux/interrupt.h
• linux/sched.h
• linux/tty.h
• linux/serial.h
• linux/tty_flip.h
• linux/slab.h
• linux/io.h
• linux/ipack.h
• ipoctal.h
• scc2698.h

Detected Declarations

• struct ipoctal_channel
• struct ipoctal
• function ipoctal_reset_channel
• function ipoctal_port_activate
• function ipoctal_install
• function ipoctal_open
• function ipoctal_reset_stats
• function ipoctal_free_channel
• function ipoctal_close
• function ipoctal_get_icount
• function ipoctal_irq_rx
• function ipoctal_irq_tx
• function ipoctal_irq_channel
• function ipoctal_irq_handler
• function ipoctal_inst_slot
• function ipoctal_copy_write_buffer
• function ipoctal_write_tty
• function ipoctal_write_room
• function ipoctal_chars_in_buffer
• function ipoctal_set_termios
• function ipoctal_hangup
• function ipoctal_shutdown
• function ipoctal_cleanup
• function ipoctal_probe
• function __ipoctal_remove
• function ipoctal_remove
• function ipoctal_init
• function ipoctal_exit
• module init ipoctal_init

Annotated Snippet

module_init(ipoctal_init);
module_exit(ipoctal_exit);

Annotation

• Immediate include surface: `linux/device.h`, `linux/module.h`, `linux/interrupt.h`, `linux/sched.h`, `linux/tty.h`, `linux/serial.h`, `linux/tty_flip.h`, `linux/slab.h`.
• Detected declarations: `struct ipoctal_channel`, `struct ipoctal`, `function ipoctal_reset_channel`, `function ipoctal_port_activate`, `function ipoctal_install`, `function ipoctal_open`, `function ipoctal_reset_stats`, `function ipoctal_free_channel`, `function ipoctal_close`, `function ipoctal_get_icount`.
• Atlas domain: Driver Families / drivers/ipack.
• 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.