arch/csky/mm/ioremap.c
Source file repositories/reference/linux-study-clean/arch/csky/mm/ioremap.c
File Facts
- System
- Linux kernel
- Corpus path
arch/csky/mm/ioremap.c- Extension
.c- Size
- 485 bytes
- Lines
- 20
- Domain
- Architecture Layer
- Bucket
- arch/csky
- 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/export.hlinux/mm.hlinux/io.h
Detected Declarations
function phys_mem_access_protexport phys_mem_access_prot
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
// Copyright (C) 2018 Hangzhou C-SKY Microsystems co.,ltd.
#include <linux/export.h>
#include <linux/mm.h>
#include <linux/io.h>
pgprot_t phys_mem_access_prot(struct file *file, unsigned long pfn,
unsigned long size, pgprot_t vma_prot)
{
if (!pfn_valid(pfn)) {
return pgprot_noncached(vma_prot);
} else if (file->f_flags & O_SYNC) {
return pgprot_writecombine(vma_prot);
}
return vma_prot;
}
EXPORT_SYMBOL(phys_mem_access_prot);
Annotation
- Immediate include surface: `linux/export.h`, `linux/mm.h`, `linux/io.h`.
- Detected declarations: `function phys_mem_access_prot`, `export phys_mem_access_prot`.
- Atlas domain: Architecture Layer / arch/csky.
- 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.