arch/mips/include/asm/video.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/video.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/video.h- Extension
.h- Size
- 875 bytes
- Lines
- 39
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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
asm/page.hasm-generic/video.h
Detected Declarations
function pgprot_framebufferfunction fb_writeqfunction fb_writeq
Annotated Snippet
#ifndef _ASM_VIDEO_H_
#define _ASM_VIDEO_H_
#include <asm/page.h>
static inline pgprot_t pgprot_framebuffer(pgprot_t prot,
unsigned long vm_start, unsigned long vm_end,
unsigned long offset)
{
return pgprot_noncached(prot);
}
#define pgprot_framebuffer pgprot_framebuffer
/*
* MIPS doesn't define __raw_ I/O macros, so the helpers
* in <asm-generic/video.h> don't generate fb_readq() and
* fb_writeq(). We have to provide them here.
*
* TODO: Convert MIPS to generic I/O. The helpers below can
* then be removed.
*/
#ifdef CONFIG_64BIT
static inline u64 fb_readq(const volatile void __iomem *addr)
{
return __raw_readq(addr);
}
#define fb_readq fb_readq
static inline void fb_writeq(u64 b, volatile void __iomem *addr)
{
__raw_writeq(b, addr);
}
#define fb_writeq fb_writeq
#endif
#include <asm-generic/video.h>
#endif /* _ASM_VIDEO_H_ */
Annotation
- Immediate include surface: `asm/page.h`, `asm-generic/video.h`.
- Detected declarations: `function pgprot_framebuffer`, `function fb_writeq`, `function fb_writeq`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.