drivers/tty/hvc/hvc_udbg.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/hvc/hvc_udbg.c

Extension

.c

Size

1403 bytes

Lines

84

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/console.h
• linux/delay.h
• linux/err.h
• linux/init.h
• linux/moduleparam.h
• linux/types.h
• linux/irq.h
• asm/udbg.h
• hvc_console.h

Detected Declarations

• function hvc_udbg_put
• function hvc_udbg_get
• function hvc_udbg_init
• function hvc_udbg_console_init
• module init hvc_udbg_init

Annotated Snippet

device_initcall(hvc_udbg_init);

static int __init hvc_udbg_console_init(void)
{
	if (!udbg_putc)
		return -ENODEV;

	hvc_instantiate(0, 0, &hvc_udbg_ops);
	add_preferred_console("hvc", 0, NULL);

	return 0;
}
console_initcall(hvc_udbg_console_init);

Annotation

• Immediate include surface: `linux/console.h`, `linux/delay.h`, `linux/err.h`, `linux/init.h`, `linux/moduleparam.h`, `linux/types.h`, `linux/irq.h`, `asm/udbg.h`.
• Detected declarations: `function hvc_udbg_put`, `function hvc_udbg_get`, `function hvc_udbg_init`, `function hvc_udbg_console_init`, `module init hvc_udbg_init`.
• Atlas domain: Driver Families / drivers/tty.
• Implementation status: integration implementation candidate.

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.