drivers/gpio/gpiolib-swnode.c

File Facts

System

Linux kernel

Corpus path

drivers/gpio/gpiolib-swnode.c

Extension

.c

Size

5297 bytes

Lines

187

Domain

Driver Families

Bucket

drivers/gpio

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/err.h
• linux/errno.h
• linux/export.h
• linux/init.h
• linux/kernel.h
• linux/printk.h
• linux/property.h
• linux/string.h
• linux/gpio/consumer.h
• linux/gpio/driver.h
• linux/gpio/property.h
• gpiolib.h
• gpiolib-swnode.h

Detected Declarations

• function swnode_gpio_get_reference
• function for_each_gpio_property_name
• function swnode_gpio_count
• function swnode_gpio_init
• function swnode_gpio_cleanup
• module init swnode_gpio_init

Annotated Snippet

subsys_initcall(swnode_gpio_init);

static void __exit swnode_gpio_cleanup(void)
{
	software_node_unregister(&swnode_gpio_undefined);
}
__exitcall(swnode_gpio_cleanup);
#endif

Annotation

• Immediate include surface: `linux/err.h`, `linux/errno.h`, `linux/export.h`, `linux/init.h`, `linux/kernel.h`, `linux/printk.h`, `linux/property.h`, `linux/string.h`.
• Detected declarations: `function swnode_gpio_get_reference`, `function for_each_gpio_property_name`, `function swnode_gpio_count`, `function swnode_gpio_init`, `function swnode_gpio_cleanup`, `module init swnode_gpio_init`.
• Atlas domain: Driver Families / drivers/gpio.
• 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.