arch/powerpc/platforms/512x/mpc512x_generic.c
Source file repositories/reference/linux-study-clean/arch/powerpc/platforms/512x/mpc512x_generic.c
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/platforms/512x/mpc512x_generic.c- Extension
.c- Size
- 938 bytes
- Lines
- 50
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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/kernel.hlinux/of.hasm/machdep.hasm/ipic.hasm/time.hmpc512x.h
Detected Declarations
function mpc512x_generic_probe
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Copyright (C) 2007,2008 Freescale Semiconductor, Inc. All rights reserved.
*
* Author: John Rigby, <jrigby@freescale.com>
*
* Description:
* MPC512x SoC setup
*/
#include <linux/kernel.h>
#include <linux/of.h>
#include <asm/machdep.h>
#include <asm/ipic.h>
#include <asm/time.h>
#include "mpc512x.h"
/*
* list of supported boards
*/
static const char * const board[] __initconst = {
"prt,prtlvt",
"fsl,mpc5125ads",
"ifm,ac14xx",
NULL
};
/*
* Called very early, MMU is off, device-tree isn't unflattened
*/
static int __init mpc512x_generic_probe(void)
{
mpc512x_init_early();
return 1;
}
define_machine(mpc512x_generic) {
.name = "MPC512x generic",
.compatibles = board,
.probe = mpc512x_generic_probe,
.init = mpc512x_init,
.setup_arch = mpc512x_setup_arch,
.init_IRQ = mpc512x_init_IRQ,
.get_irq = ipic_get_irq,
.restart = mpc512x_restart,
};
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/of.h`, `asm/machdep.h`, `asm/ipic.h`, `asm/time.h`, `mpc512x.h`.
- Detected declarations: `function mpc512x_generic_probe`.
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.