arch/arm/mach-tegra/irq.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-tegra/irq.c

Extension

.c

Size

2014 bytes

Lines

96

Domain

Architecture Layer

Bucket

arch/arm

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/cpu_pm.h
• linux/interrupt.h
• linux/io.h
• linux/irqchip/arm-gic.h
• linux/irq.h
• linux/kernel.h
• linux/of_address.h
• linux/of.h
• linux/syscore_ops.h
• soc/tegra/irq.h
• board.h
• iomap.h

Detected Declarations

• function tegra_pending_sgi
• function tegra_gic_notifier
• function tegra114_gic_cpu_pm_registration
• function tegra114_gic_cpu_pm_registration
• function tegra_init_irq

Annotated Snippet

static void __init tegra114_gic_cpu_pm_registration(void) { }
#endif

static const struct of_device_id tegra_ictlr_match[] __initconst = {
	{ .compatible = "nvidia,tegra20-ictlr" },
	{ .compatible = "nvidia,tegra30-ictlr" },
	{ }
};

void __init tegra_init_irq(void)
{
	if (WARN_ON(!of_find_matching_node(NULL, tegra_ictlr_match)))
		pr_warn("Outdated DT detected, suspend/resume will NOT work\n");

	tegra114_gic_cpu_pm_registration();
}

Annotation

• Immediate include surface: `linux/cpu_pm.h`, `linux/interrupt.h`, `linux/io.h`, `linux/irqchip/arm-gic.h`, `linux/irq.h`, `linux/kernel.h`, `linux/of_address.h`, `linux/of.h`.
• Detected declarations: `function tegra_pending_sgi`, `function tegra_gic_notifier`, `function tegra114_gic_cpu_pm_registration`, `function tegra114_gic_cpu_pm_registration`, `function tegra_init_irq`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.