drivers/tty/serial/timbuart.h
Source file repositories/reference/linux-study-clean/drivers/tty/serial/timbuart.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/tty/serial/timbuart.h- Extension
.h- Size
- 925 bytes
- Lines
- 47
- Domain
- Driver Families
- Bucket
- drivers/tty
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _TIMBUART_H
#define _TIMBUART_H
#define TIMBUART_FIFO_SIZE 2048
#define TIMBUART_RXFIFO 0x08
#define TIMBUART_TXFIFO 0x0c
#define TIMBUART_IER 0x10
#define TIMBUART_IPR 0x14
#define TIMBUART_ISR 0x18
#define TIMBUART_CTRL 0x1c
#define TIMBUART_BAUDRATE 0x20
#define TIMBUART_CTRL_RTS 0x01
#define TIMBUART_CTRL_CTS 0x02
#define TIMBUART_CTRL_FLSHTX 0x40
#define TIMBUART_CTRL_FLSHRX 0x80
#define TXBF 0x01
#define TXBAE 0x02
#define CTS_DELTA 0x04
#define RXDP 0x08
#define RXBAF 0x10
#define RXBF 0x20
#define RXTT 0x40
#define RXBNAE 0x80
#define TXBE 0x100
#define RXFLAGS (RXDP | RXBAF | RXBF | RXTT | RXBNAE)
#define TXFLAGS (TXBF | TXBAE)
#define TIMBUART_MAJOR 204
#define TIMBUART_MINOR 192
#endif /* _TIMBUART_H */
Annotation
- Atlas domain: Driver Families / drivers/tty.
- Implementation status: source 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.