arch/arm/mach-mvebu/dove.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-mvebu/dove.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-mvebu/dove.c- Extension
.c- Size
- 726 bytes
- Lines
- 37
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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/init.hlinux/mbus.hlinux/of.hlinux/soc/dove/pmu.hasm/hardware/cache-tauros2.hasm/mach/arch.hcommon.h
Detected Declarations
function dove_init
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* arch/arm/mach-mvebu/dove.c
*
* Marvell Dove 88AP510 System On Chip FDT Board
*/
#include <linux/init.h>
#include <linux/mbus.h>
#include <linux/of.h>
#include <linux/soc/dove/pmu.h>
#include <asm/hardware/cache-tauros2.h>
#include <asm/mach/arch.h>
#include "common.h"
static void __init dove_init(void)
{
pr_info("Dove 88AP510 SoC\n");
#ifdef CONFIG_CACHE_TAUROS2
tauros2_init(0);
#endif
BUG_ON(mvebu_mbus_dt_init(false));
dove_init_pmu();
}
static const char * const dove_dt_compat[] __initconst = {
"marvell,dove",
NULL
};
DT_MACHINE_START(DOVE_DT, "Marvell Dove")
.init_machine = dove_init,
.restart = mvebu_restart,
.dt_compat = dove_dt_compat,
MACHINE_END
Annotation
- Immediate include surface: `linux/init.h`, `linux/mbus.h`, `linux/of.h`, `linux/soc/dove/pmu.h`, `asm/hardware/cache-tauros2.h`, `asm/mach/arch.h`, `common.h`.
- Detected declarations: `function dove_init`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.