arch/mips/cobalt/reset.c

File Facts

System

Linux kernel

Corpus path

arch/mips/cobalt/reset.c

Extension

.c

Size

1090 bytes

Lines

53

Domain

Architecture Layer

Bucket

arch/mips

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.

Dependency Surface

• linux/init.h
• linux/io.h
• linux/leds.h
• asm/idle.h
• asm/processor.h
• cobalt.h

Detected Declarations

• function ledtrig_power_off_init
• function cobalt_machine_halt
• function cobalt_machine_restart
• module init ledtrig_power_off_init

Annotated Snippet

device_initcall(ledtrig_power_off_init);

void cobalt_machine_halt(void)
{
	/*
	 * turn on power off LED on RaQ
	 */
	led_trigger_event(power_off_led_trigger, LED_FULL);

	local_irq_disable();
	while (1) {
		if (cpu_wait)
			cpu_wait();
	}
}

void cobalt_machine_restart(char *command)
{
	writeb(RESET, RESET_PORT);

	/* we should never get here */
	cobalt_machine_halt();
}

Annotation

• Immediate include surface: `linux/init.h`, `linux/io.h`, `linux/leds.h`, `asm/idle.h`, `asm/processor.h`, `cobalt.h`.
• Detected declarations: `function ledtrig_power_off_init`, `function cobalt_machine_halt`, `function cobalt_machine_restart`, `module init ledtrig_power_off_init`.
• Atlas domain: Architecture Layer / arch/mips.
• Implementation status: integration 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.