arch/powerpc/boot/fsl-soc.c
Source file repositories/reference/linux-study-clean/arch/powerpc/boot/fsl-soc.c
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/boot/fsl-soc.c- Extension
.c- Size
- 966 bytes
- Lines
- 55
- 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
ops.htypes.hfsl-soc.hstdio.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Freescale SOC support functions
*
* Author: Scott Wood <scottwood@freescale.com>
*
* Copyright (c) 2007 Freescale Semiconductor, Inc.
*/
#include "ops.h"
#include "types.h"
#include "fsl-soc.h"
#include "stdio.h"
static u32 prop_buf[MAX_PROP_LEN / 4];
u32 *fsl_get_immr(void)
{
void *soc;
unsigned long ret = 0;
soc = find_node_by_devtype(NULL, "soc");
if (soc) {
int size;
u32 naddr;
size = getprop(soc, "#address-cells", prop_buf, MAX_PROP_LEN);
if (size == 4)
naddr = prop_buf[0];
else
naddr = 2;
if (naddr != 1 && naddr != 2)
goto err;
size = getprop(soc, "ranges", prop_buf, MAX_PROP_LEN);
if (size < 12)
goto err;
if (prop_buf[0] != 0)
goto err;
if (naddr == 2 && prop_buf[1] != 0)
goto err;
if (!dt_xlate_addr(soc, prop_buf + naddr, 8, &ret))
ret = 0;
}
err:
if (!ret)
printf("fsl_get_immr: Failed to find immr base\r\n");
return (u32 *)ret;
}
Annotation
- Immediate include surface: `ops.h`, `types.h`, `fsl-soc.h`, `stdio.h`.
- 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.