arch/mips/rb532/serial.c
Source file repositories/reference/linux-study-clean/arch/mips/rb532/serial.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/rb532/serial.c- Extension
.c- Size
- 1926 bytes
- Lines
- 55
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/init.hlinux/tty.hlinux/serial_core.hlinux/serial_8250.hlinux/irq.hasm/serial.hasm/mach-rc32434/rb.h
Detected Declarations
function setup_serial_port
Annotated Snippet
#include <linux/init.h>
#include <linux/tty.h>
#include <linux/serial_core.h>
#include <linux/serial_8250.h>
#include <linux/irq.h>
#include <asm/serial.h>
#include <asm/mach-rc32434/rb.h>
extern unsigned int idt_cpu_freq;
static struct uart_port rb532_uart = {
.flags = UPF_BOOT_AUTOCONF,
.line = 0,
.irq = UART0_IRQ,
.iotype = UPIO_MEM,
.membase = (char *)KSEG1ADDR(REGBASE + UART0BASE),
.regshift = 2
};
static int __init setup_serial_port(void)
{
rb532_uart.uartclk = idt_cpu_freq;
return early_serial_setup(&rb532_uart);
}
arch_initcall(setup_serial_port);
Annotation
- Immediate include surface: `linux/init.h`, `linux/tty.h`, `linux/serial_core.h`, `linux/serial_8250.h`, `linux/irq.h`, `asm/serial.h`, `asm/mach-rc32434/rb.h`.
- Detected declarations: `function setup_serial_port`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.