drivers/gpio/gpio-pci-idio-16.c

File Facts

System

Linux kernel

Corpus path

drivers/gpio/gpio-pci-idio-16.c

Extension

.c

Size

3663 bytes

Lines

117

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bits.h
• linux/device.h
• linux/err.h
• linux/irq.h
• linux/kernel.h
• linux/module.h
• linux/pci.h
• linux/regmap.h
• linux/types.h
• gpio-idio-16.h

Detected Declarations

• function idio_16_probe

Annotated Snippet

static struct pci_driver idio_16_driver = {
	.name = "pci-idio-16",
	.id_table = idio_16_pci_dev_id,
	.probe = idio_16_probe
};

module_pci_driver(idio_16_driver);

MODULE_AUTHOR("William Breathitt Gray <vilhelm.gray@gmail.com>");
MODULE_DESCRIPTION("ACCES PCI-IDIO-16 GPIO driver");
MODULE_LICENSE("GPL v2");
MODULE_IMPORT_NS("GPIO_IDIO_16");

Annotation

• Immediate include surface: `linux/bits.h`, `linux/device.h`, `linux/err.h`, `linux/irq.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/regmap.h`.
• Detected declarations: `function idio_16_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.