drivers/gpio/gpio-merrifield.c

File Facts

System

Linux kernel

Corpus path

drivers/gpio/gpio-merrifield.c

Extension

.c

Size

3788 bytes

Lines

146

Domain

Driver Families

Bucket

drivers/gpio

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/acpi.h
• linux/bitops.h
• linux/device.h
• linux/err.h
• linux/io.h
• linux/module.h
• linux/pci.h
• linux/types.h
• gpio-tangier.h

Detected Declarations

• function mrfld_gpio_probe

Annotated Snippet

static struct pci_driver mrfld_gpio_driver = {
	.name		= "gpio-merrifield",
	.id_table	= mrfld_gpio_ids,
	.probe		= mrfld_gpio_probe,
};
module_pci_driver(mrfld_gpio_driver);

MODULE_AUTHOR("Andy Shevchenko <andriy.shevchenko@linux.intel.com>");
MODULE_DESCRIPTION("Intel Merrifield SoC GPIO driver");
MODULE_LICENSE("GPL v2");
MODULE_IMPORT_NS("GPIO_TANGIER");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitops.h`, `linux/device.h`, `linux/err.h`, `linux/io.h`, `linux/module.h`, `linux/pci.h`, `linux/types.h`.
• Detected declarations: `function mrfld_gpio_probe`.
• Atlas domain: Driver Families / drivers/gpio.
• 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.