drivers/pinctrl/bcm/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/bcm/Makefile

Extension

[no extension]

Size

1013 bytes

Lines

22

Domain

Driver Families

Bucket

drivers/pinctrl

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0
# Broadcom pinctrl support

obj-$(CONFIG_PINCTRL_BCM281XX)		+= pinctrl-bcm281xx.o
obj-$(CONFIG_PINCTRL_BCM2835)		+= pinctrl-bcm2835.o
obj-$(CONFIG_PINCTRL_BCM4908)		+= pinctrl-bcm4908.o
obj-$(CONFIG_PINCTRL_BCM63XX)		+= pinctrl-bcm63xx.o
obj-$(CONFIG_PINCTRL_BCM6318)		+= pinctrl-bcm6318.o
obj-$(CONFIG_PINCTRL_BCM6328)		+= pinctrl-bcm6328.o
obj-$(CONFIG_PINCTRL_BCM6358)		+= pinctrl-bcm6358.o
obj-$(CONFIG_PINCTRL_BCM6362)		+= pinctrl-bcm6362.o
obj-$(CONFIG_PINCTRL_BCM6368)		+= pinctrl-bcm6368.o
obj-$(CONFIG_PINCTRL_BCM63268)		+= pinctrl-bcm63268.o
obj-$(CONFIG_PINCTRL_BRCMSTB)		+= pinctrl-brcmstb.o
obj-$(CONFIG_PINCTRL_BCM2712)		+= pinctrl-brcmstb-bcm2712.o
obj-$(CONFIG_PINCTRL_IPROC_GPIO)	+= pinctrl-iproc-gpio.o
obj-$(CONFIG_PINCTRL_CYGNUS_MUX)	+= pinctrl-cygnus-mux.o
obj-$(CONFIG_PINCTRL_NS)		+= pinctrl-ns.o
obj-$(CONFIG_PINCTRL_NSP_GPIO)		+= pinctrl-nsp-gpio.o
obj-$(CONFIG_PINCTRL_NS2_MUX)		+= pinctrl-ns2-mux.o
obj-$(CONFIG_PINCTRL_NSP_MUX)		+= pinctrl-nsp-mux.o

Annotation

• Atlas domain: Driver Families / drivers/pinctrl.
• Implementation status: atlas-only.

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.