drivers/pinctrl/intel/pinctrl-denverton.c

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/intel/pinctrl-denverton.c

Extension

.c

Size

8871 bytes

Lines

284

Domain

Driver Families

Bucket

drivers/pinctrl

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• 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/mod_devicetable.h
• linux/module.h
• linux/platform_device.h
• linux/pm.h
• linux/pinctrl/pinctrl.h
• pinctrl-intel.h

Detected Declarations

• function dnv_pinctrl_init
• function dnv_pinctrl_exit
• module init dnv_pinctrl_init

Annotated Snippet

subsys_initcall(dnv_pinctrl_init);

static void __exit dnv_pinctrl_exit(void)
{
	platform_driver_unregister(&dnv_pinctrl_driver);
}
module_exit(dnv_pinctrl_exit);

MODULE_AUTHOR("Mika Westerberg <mika.westerberg@linux.intel.com>");
MODULE_DESCRIPTION("Intel Denverton SoC pinctrl/GPIO driver");
MODULE_LICENSE("GPL v2");
MODULE_IMPORT_NS("PINCTRL_INTEL");

Annotation

• Immediate include surface: `linux/mod_devicetable.h`, `linux/module.h`, `linux/platform_device.h`, `linux/pm.h`, `linux/pinctrl/pinctrl.h`, `pinctrl-intel.h`.
• Detected declarations: `function dnv_pinctrl_init`, `function dnv_pinctrl_exit`, `module init dnv_pinctrl_init`.
• Atlas domain: Driver Families / drivers/pinctrl.
• 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.