arch/mips/sni/reset.c
Source file repositories/reference/linux-study-clean/arch/mips/sni/reset.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/sni/reset.c- Extension
.c- Size
- 963 bytes
- Lines
- 49
- 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.
Dependency Surface
linux/delay.hasm/io.hasm/reboot.hasm/sni.h
Detected Declarations
function kb_waitfunction sni_machine_restartfunction sni_machine_power_off
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* linux/arch/mips/sni/process.c
*
* Reset a SNI machine.
*/
#include <linux/delay.h>
#include <asm/io.h>
#include <asm/reboot.h>
#include <asm/sni.h>
/*
* This routine reboots the machine by asking the keyboard
* controller to pulse the reset-line low. We try that for a while,
* and if it doesn't work, we do some other stupid things.
*/
static inline void kb_wait(void)
{
int i;
for (i = 0; i < 0x10000; i++)
if ((inb_p(0x64) & 0x02) == 0)
break;
}
/* XXX This ends up at the ARC firmware prompt ... */
void sni_machine_restart(char *command)
{
int i;
/* This does a normal via the keyboard controller like a PC.
We can do that easier ... */
local_irq_disable();
for (;;) {
for (i = 0; i < 100; i++) {
kb_wait();
udelay(50);
outb_p(0xfe, 0x64); /* pulse reset low */
udelay(50);
}
}
}
void sni_machine_power_off(void)
{
*(volatile unsigned char *)PCIMT_CSWCSM = 0xfd;
}
Annotation
- Immediate include surface: `linux/delay.h`, `asm/io.h`, `asm/reboot.h`, `asm/sni.h`.
- Detected declarations: `function kb_wait`, `function sni_machine_restart`, `function sni_machine_power_off`.
- 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.