arch/sparc/video/video-common.c

File Facts

System

Linux kernel

Corpus path

arch/sparc/video/video-common.c

Extension

.c

Size

483 bytes

Lines

26

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/console.h
• linux/device.h
• linux/module.h
• asm/prom.h
• asm/video.h

Detected Declarations

• function video_is_primary_device
• export video_is_primary_device

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0

#include <linux/console.h>
#include <linux/device.h>
#include <linux/module.h>

#include <asm/prom.h>
#include <asm/video.h>

bool video_is_primary_device(struct device *dev)
{
	struct device_node *node = dev->of_node;

	if (console_set_on_cmdline)
		return false;

	if (node && node == of_console_device)
		return true;

	return false;
}
EXPORT_SYMBOL(video_is_primary_device);

MODULE_DESCRIPTION("Sparc video helpers");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/console.h`, `linux/device.h`, `linux/module.h`, `asm/prom.h`, `asm/video.h`.
• Detected declarations: `function video_is_primary_device`, `export video_is_primary_device`.
• 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.