arch/sparc/prom/ranges.c

File Facts

System

Linux kernel

Corpus path

arch/sparc/prom/ranges.c

Extension

.c

Size

3759 bytes

Lines

115

Domain

Architecture Layer

Bucket

arch/sparc

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/module.h
• asm/openprom.h
• asm/oplib.h
• asm/types.h

Detected Declarations

• function prom_adjust_regs
• function prom_adjust_ranges
• function prom_apply_obio_ranges
• function prom_ranges_init
• function prom_apply_generic_ranges
• export prom_apply_obio_ranges

Annotated Snippet

if (parent) {
			struct linux_prom_ranges parent_ranges[PROMREG_MAX];
			int num_parent_ranges;

			success = prom_getproperty(parent, "ranges",
						   (char *) parent_ranges,
						   sizeof(parent_ranges));
			if (success != -1) {
				num_parent_ranges = (success / sizeof(struct linux_prom_ranges));
				prom_adjust_ranges(ranges, num_ranges, parent_ranges, num_parent_ranges);
			}
		}
		prom_adjust_regs(regs, nregs, ranges, num_ranges);
	}
}

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `asm/openprom.h`, `asm/oplib.h`, `asm/types.h`.
• Detected declarations: `function prom_adjust_regs`, `function prom_adjust_ranges`, `function prom_apply_obio_ranges`, `function prom_ranges_init`, `function prom_apply_generic_ranges`, `export prom_apply_obio_ranges`.
• Atlas domain: Architecture Layer / arch/sparc.
• 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.