drivers/tty/serial/sifive.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/sifive.c

Extension

.c

Size

31841 bytes

Lines

1151

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.
• 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/clk.h
• linux/console.h
• linux/delay.h
• linux/init.h
• linux/io.h
• linux/irq.h
• linux/module.h
• linux/of.h
• linux/of_irq.h
• linux/platform_device.h
• linux/serial_core.h
• linux/serial_reg.h
• linux/slab.h
• linux/tty.h
• linux/tty_flip.h

Detected Declarations

• struct sifive_serial_port
• function __ssp_early_writel
• function __ssp_early_readl
• function __ssp_writel
• function __ssp_readl
• function sifive_serial_is_txfifo_full
• function __ssp_transmit_char
• function __ssp_transmit_chars
• function __ssp_enable_txwm
• function __ssp_enable_rxwm
• function __ssp_disable_txwm
• function __ssp_disable_rxwm
• function __ssp_receive_char
• function __ssp_receive_chars
• function __ssp_update_div
• function __ssp_update_baud_rate
• function __ssp_set_stop_bits
• function __ssp_wait_for_xmitr
• function sifive_serial_stop_tx
• function sifive_serial_stop_rx
• function sifive_serial_start_tx
• function sifive_serial_irq
• function sifive_serial_tx_empty
• function sifive_serial_get_mctrl
• function sifive_serial_set_mctrl
• function sifive_serial_shutdown
• function sifive_serial_clk_notifier
• function sifive_serial_set_termios
• function sifive_serial_release_port
• function sifive_serial_config_port
• function sifive_serial_verify_port
• function sifive_serial_poll_get_char
• function sifive_serial_poll_put_char
• function early_sifive_serial_putc
• function early_sifive_serial_write
• function early_sifive_serial_setup
• function sifive_serial_console_putchar
• function sifive_serial_device_lock
• function sifive_serial_device_unlock
• function sifive_serial_console_write_atomic
• function sifive_serial_console_write_thread
• function sifive_serial_console_setup
• function sifive_console_init
• function __ssp_add_console_port
• function __ssp_remove_console_port
• function __ssp_add_console_port
• function sifive_serial_probe
• function sifive_serial_remove

Annotated Snippet

module_init(sifive_serial_init);
module_exit(sifive_serial_exit);

MODULE_DESCRIPTION("SiFive UART serial driver");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Paul Walmsley <paul@pwsan.com>");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/console.h`, `linux/delay.h`, `linux/init.h`, `linux/io.h`, `linux/irq.h`, `linux/module.h`, `linux/of.h`.
• Detected declarations: `struct sifive_serial_port`, `function __ssp_early_writel`, `function __ssp_early_readl`, `function __ssp_writel`, `function __ssp_readl`, `function sifive_serial_is_txfifo_full`, `function __ssp_transmit_char`, `function __ssp_transmit_chars`, `function __ssp_enable_txwm`, `function __ssp_enable_rxwm`.
• Atlas domain: Driver Families / drivers/tty.
• Implementation status: integration implementation candidate.
• 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.