arch/arm/mach-omap1/gpio16xx.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-omap1/gpio16xx.c

Extension

.c

Size

6574 bytes

Lines

252

Domain

Architecture Layer

Bucket

arch/arm

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/platform_data/gpio-omap.h
• linux/property.h
• linux/soc/ti/omap1-io.h
• hardware.h
• irqs.h
• soc.h

Detected Declarations

• function omap16xx_gpio_init

Annotated Snippet

if (unlikely(!res)) {
			pr_err("%s.%d: Invalid mem resource.\n", pdevinfo->name, pdevinfo->id);
			return -ENODEV;
		}

		base = ioremap(res->start, resource_size(res));
		if (unlikely(!base)) {
			pr_err("%s.%d: ioremap failed.\n", pdevinfo->name, pdevinfo->id);
			return -ENOMEM;
		}

		__raw_writel(SYSCONFIG_WORD, base + OMAP1610_GPIO_SYSCONFIG);
		iounmap(base);

		platform_device_register_full(omap16xx_gpio_dev[i]);
	}

	return 0;
}
postcore_initcall(omap16xx_gpio_init);

Annotation

• Immediate include surface: `linux/platform_data/gpio-omap.h`, `linux/property.h`, `linux/soc/ti/omap1-io.h`, `hardware.h`, `irqs.h`, `soc.h`.
• Detected declarations: `function omap16xx_gpio_init`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.