drivers/mtd/nand/raw/denali_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/mtd/nand/raw/denali_pci.c

Extension

.c

Size

3419 bytes

Lines

140

Domain

Driver Families

Bucket

drivers/mtd

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/errno.h
• linux/io.h
• linux/kernel.h
• linux/module.h
• linux/pci.h
• denali.h

Detected Declarations

• function denali_pci_probe
• function denali_pci_remove

Annotated Snippet

static struct pci_driver denali_pci_driver = {
	.name = DENALI_NAND_NAME,
	.id_table = denali_pci_ids,
	.probe = denali_pci_probe,
	.remove = denali_pci_remove,
};
module_pci_driver(denali_pci_driver);

MODULE_DESCRIPTION("PCI driver for Denali NAND controller");
MODULE_AUTHOR("Intel Corporation and its suppliers");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/io.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `denali.h`.
• Detected declarations: `function denali_pci_probe`, `function denali_pci_remove`.
• Atlas domain: Driver Families / drivers/mtd.
• Implementation status: pattern 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.