drivers/pinctrl/bcm/pinctrl-bcm63xx.c

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/bcm/pinctrl-bcm63xx.c

Extension

.c

Size

2820 bytes

Lines

108

Domain

Driver Families

Bucket

drivers/pinctrl

Inferred role

Driver Families: implementation source

Status

source 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.
• 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/gpio/regmap.h
• linux/mfd/syscon.h
• linux/mod_devicetable.h
• linux/of.h
• linux/platform_device.h
• pinctrl-bcm63xx.h

Detected Declarations

• function unit
• function bcm63xx_gpio_probe
• function bcm63xx_pinctrl_probe
• function for_each_child_of_node_scoped

Annotated Snippet

if (of_match_node(bcm63xx_gpio_of_match, node)) {
			err = bcm63xx_gpio_probe(dev, node, soc, pc);
			if (err) {
				dev_err(dev, "could not add GPIO chip\n");
				return err;
			}
		}
	}

	return 0;
}

Annotation

• Immediate include surface: `linux/gpio/regmap.h`, `linux/mfd/syscon.h`, `linux/mod_devicetable.h`, `linux/of.h`, `linux/platform_device.h`, `pinctrl-bcm63xx.h`.
• Detected declarations: `function unit`, `function bcm63xx_gpio_probe`, `function bcm63xx_pinctrl_probe`, `function for_each_child_of_node_scoped`.
• Atlas domain: Driver Families / drivers/pinctrl.
• Implementation status: source 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.