drivers/tty/ehv_bytechan.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/ehv_bytechan.c

Extension

.c

Size

22332 bytes

Lines

821

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/init.h
• linux/slab.h
• linux/err.h
• linux/interrupt.h
• linux/fs.h
• linux/poll.h
• asm/epapr_hcalls.h
• linux/of.h
• linux/of_irq.h
• linux/platform_device.h
• linux/cdev.h
• linux/console.h
• linux/tty.h
• linux/tty_flip.h
• linux/circ_buf.h
• asm/udbg.h

Detected Declarations

• struct ehv_bc_data
• function enable_irq
• function disable_tx_interrupt
• function find_console_handle
• function local_ev_byte_channel_send
• function ev_byte_channel_send
• function byte_channel_spin_send
• function ehv_bc_udbg_putc
• function characters
• function ehv_bc_console_byte_channel_send
• function printk
• function ehv_bc_console_init
• function ehv_bc_tty_rx_isr
• function ehv_bc_tx_dequeue
• function ehv_bc_tty_tx_isr
• function ehv_bc_tty_write_room
• function registered
• function ehv_bc_tty_close
• function ehv_bc_tty_write_room
• function ehv_bc_tty_throttle
• function ehv_bc_tty_throttle
• function ehv_bc_tty_hangup
• function ehv_bc_tty_open
• function ehv_bc_tty_port_shutdown
• function ehv_bc_tty_probe
• function ehv_bc_init
• module init ehv_bc_init

Annotated Snippet

device_initcall(ehv_bc_init);

Annotation

• Immediate include surface: `linux/init.h`, `linux/slab.h`, `linux/err.h`, `linux/interrupt.h`, `linux/fs.h`, `linux/poll.h`, `asm/epapr_hcalls.h`, `linux/of.h`.
• Detected declarations: `struct ehv_bc_data`, `function enable_irq`, `function disable_tx_interrupt`, `function find_console_handle`, `function local_ev_byte_channel_send`, `function ev_byte_channel_send`, `function byte_channel_spin_send`, `function ehv_bc_udbg_putc`, `function characters`, `function ehv_bc_console_byte_channel_send`.
• 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.