arch/parisc/video/video-sti.c
Source file repositories/reference/linux-study-clean/arch/parisc/video/video-sti.c
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/video/video-sti.c- Extension
.c- Size
- 650 bytes
- Lines
- 28
- Domain
- Architecture Layer
- Bucket
- arch/parisc
- 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/module.hvideo/sticore.hasm/video.h
Detected Declarations
function Copyrightexport video_is_primary_device
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright (C) 2000 Philipp Rumpf <prumpf@tux.org>
* Copyright (C) 2001-2020 Helge Deller <deller@gmx.de>
* Copyright (C) 2001-2002 Thomas Bogendoerfer <tsbogend@alpha.franken.de>
*/
#include <linux/module.h>
#include <video/sticore.h>
#include <asm/video.h>
bool video_is_primary_device(struct device *dev)
{
struct sti_struct *sti;
sti = sti_get_rom(0);
/* if no built-in graphics card found, allow any fb driver as default */
if (!sti)
return true;
/* return true if it's the default built-in framebuffer driver */
return (sti->dev == dev);
}
EXPORT_SYMBOL(video_is_primary_device);
Annotation
- Immediate include surface: `linux/module.h`, `video/sticore.h`, `asm/video.h`.
- Detected declarations: `function Copyright`, `export video_is_primary_device`.
- Atlas domain: Architecture Layer / arch/parisc.
- 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.