arch/sh/kernel/cpu/irq/ipr.c

File Facts

System

Linux kernel

Corpus path

arch/sh/kernel/cpu/irq/ipr.c

Extension

.c

Size

2489 bytes

Lines

81

Domain

Architecture Layer

Bucket

arch/sh

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/init.h
• linux/interrupt.h
• linux/io.h
• linux/irq.h
• linux/kernel.h
• linux/module.h
• linux/topology.h

Detected Declarations

• function Copyright
• function disable_ipr_irq
• function enable_ipr_irq
• function register_ipr_controller
• export register_ipr_controller

Annotated Snippet

if (unlikely(res != p->irq && res != -EEXIST)) {
			printk(KERN_INFO "can not get irq_desc for %d\n",
			       p->irq);
			continue;
		}

		disable_irq_nosync(p->irq);
		irq_set_chip_and_handler_name(p->irq, &desc->chip,
					      handle_level_irq, "level");
		irq_set_chip_data(p->irq, p);
		disable_ipr_irq(irq_get_irq_data(p->irq));
	}
}
EXPORT_SYMBOL(register_ipr_controller);

Annotation

• Immediate include surface: `linux/init.h`, `linux/interrupt.h`, `linux/io.h`, `linux/irq.h`, `linux/kernel.h`, `linux/module.h`, `linux/topology.h`.
• Detected declarations: `function Copyright`, `function disable_ipr_irq`, `function enable_ipr_irq`, `function register_ipr_controller`, `export register_ipr_controller`.
• Atlas domain: Architecture Layer / arch/sh.
• 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.