arch/mips/lantiq/xway/vmmc.c

File Facts

System

Linux kernel

Corpus path

arch/mips/lantiq/xway/vmmc.c

Extension

.c

Size

1492 bytes

Lines

72

Domain

Architecture Layer

Bucket

arch/mips

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/err.h
• linux/export.h
• linux/gpio/consumer.h
• linux/mod_devicetable.h
• linux/platform_device.h
• linux/dma-mapping.h
• lantiq_soc.h

Detected Declarations

• function vmmc_probe
• export ltq_get_cp1_base

Annotated Snippet

if (error) {
			dev_err(&pdev->dev,
				"failed to request GPIO idx %d: %d\n",
				gpio_count, error);
			continue;
		}

		gpiod_set_consumer_name(gpio, "vmmc-relay");
	}

	dev_info(&pdev->dev, "reserved %dMB at 0x%p", CP1_SIZE >> 20, cp1_base);

	return 0;
}

static const struct of_device_id vmmc_match[] = {
	{ .compatible = "lantiq,vmmc-xway" },
	{},
};

static struct platform_driver vmmc_driver = {
	.probe = vmmc_probe,
	.driver = {
		.name = "lantiq,vmmc",
		.of_match_table = vmmc_match,
	},
};
builtin_platform_driver(vmmc_driver);

Annotation

• Immediate include surface: `linux/err.h`, `linux/export.h`, `linux/gpio/consumer.h`, `linux/mod_devicetable.h`, `linux/platform_device.h`, `linux/dma-mapping.h`, `lantiq_soc.h`.
• Detected declarations: `function vmmc_probe`, `export ltq_get_cp1_base`.
• Atlas domain: Architecture Layer / arch/mips.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.