drivers/staging/greybus/uart.c

File Facts

System

Linux kernel

Corpus path

drivers/staging/greybus/uart.c

Extension

.c

Size

25755 bytes

Lines

1030

Domain

Driver Families

Bucket

drivers/staging

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.
• 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/kernel.h
• linux/errno.h
• linux/module.h
• linux/sched/signal.h
• linux/wait.h
• linux/slab.h
• linux/uaccess.h
• linux/mutex.h
• linux/tty.h
• linux/serial.h
• linux/tty_driver.h
• linux/tty_flip.h
• linux/idr.h
• linux/fs.h
• linux/kdev_t.h
• linux/kfifo.h
• linux/workqueue.h
• linux/completion.h
• linux/greybus.h
• gbphy.h

Detected Declarations

• struct gb_tty
• function gb_uart_receive_data_handler
• function gb_uart_serial_state_handler
• function gb_uart_receive_credits_handler
• function gb_uart_request_handler
• function gb_uart_tx_write_work
• function send_line_coding
• function send_control
• function send_break
• function gb_uart_wait_for_all_credits
• function gb_uart_flush
• function alloc_minor
• function release_minor
• function gb_tty_install
• function gb_tty_open
• function gb_tty_close
• function gb_tty_cleanup
• function gb_tty_hangup
• function gb_tty_write
• function gb_tty_write_room
• function gb_tty_chars_in_buffer
• function gb_tty_break_ctl
• function gb_tty_set_termios
• function gb_tty_tiocmget
• function gb_tty_tiocmset
• function gb_tty_throttle
• function gb_tty_unthrottle
• function get_serial_info
• function set_serial_info
• function wait_serial_change
• function gb_tty_get_icount
• function gb_tty_ioctl
• function gb_tty_dtr_rts
• function gb_tty_port_activate
• function gb_tty_port_shutdown
• function gb_tty_port_destruct
• function gb_uart_probe
• function gb_uart_remove
• function gb_tty_init
• function gb_tty_exit
• function gb_uart_driver_init
• function gb_uart_driver_exit
• module init gb_uart_driver_init

Annotated Snippet

module_init(gb_uart_driver_init);

static void gb_uart_driver_exit(void)
{
	gb_gbphy_deregister(&uart_driver);
	gb_tty_exit();
}

module_exit(gb_uart_driver_exit);
MODULE_DESCRIPTION("UART driver for the Greybus 'generic' UART module");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/module.h`, `linux/sched/signal.h`, `linux/wait.h`, `linux/slab.h`, `linux/uaccess.h`, `linux/mutex.h`.
• Detected declarations: `struct gb_tty`, `function gb_uart_receive_data_handler`, `function gb_uart_serial_state_handler`, `function gb_uart_receive_credits_handler`, `function gb_uart_request_handler`, `function gb_uart_tx_write_work`, `function send_line_coding`, `function send_control`, `function send_break`, `function gb_uart_wait_for_all_credits`.
• Atlas domain: Driver Families / drivers/staging.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.