include/linux/platform_data/serial-omap.h
Source file repositories/reference/linux-study-clean/include/linux/platform_data/serial-omap.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/platform_data/serial-omap.h- Extension
.h- Size
- 1024 bytes
- Lines
- 43
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/serial_core.hlinux/device.hlinux/pm_qos.h
Detected Declarations
struct omap_uart_port_info
Annotated Snippet
struct omap_uart_port_info {
bool dma_enabled; /* To specify DMA Mode */
unsigned int uartclk; /* UART clock rate */
upf_t flags; /* UPF_* flags */
unsigned int dma_rx_buf_size;
unsigned int dma_rx_timeout;
unsigned int autosuspend_timeout;
unsigned int dma_rx_poll_rate;
int (*get_context_loss_count)(struct device *);
void (*enable_wakeup)(struct device *, bool);
};
#endif /* __OMAP_SERIAL_H__ */
Annotation
- Immediate include surface: `linux/serial_core.h`, `linux/device.h`, `linux/pm_qos.h`.
- Detected declarations: `struct omap_uart_port_info`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.