drivers/acpi/riscv/init.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/riscv/init.c

Extension

.c

Size

324 bytes

Lines

16

Domain

Driver Families

Bucket

drivers/acpi

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

• linux/acpi.h
• init.h

Detected Declarations

• function Copyright

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * Copyright (C) 2023-2024, Ventana Micro Systems Inc
 *	Author: Sunil V L <sunilvl@ventanamicro.com>
 */

#include <linux/acpi.h>
#include "init.h"

void __init acpi_arch_init(void)
{
	riscv_acpi_init_gsi_mapping();
	if (IS_ENABLED(CONFIG_ACPI_RIMT))
		riscv_acpi_rimt_init();
}

Annotation

• Immediate include surface: `linux/acpi.h`, `init.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Driver Families / drivers/acpi.
• 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.